Onboard me to Signet locally. Follow the README at
https://github.com/kaan7305/dispatch
pipx install git+https://github.com/kaan7305/dispatch.git
dispatch login
An instructor sends one task to the whole room. Each seat decides for itself. Track the status of each dispatch, for each seat.
Company A runs Claude Code on a Mac. Company B runs Codex on Windows. One signed dispatch crosses between them. You compose, the far side approves, both keep their own logs.
Every one of these has the same shape: the work has to happen on a machine you aren't sitting at, because the software, the hardware, or the data lives there and can't move.
Each trust edge (made when someone accepts your invitation) carries a scope. You set it, change it any time, revoke it outright. Try adjusting one:
Every dispatch carries an Ed25519 signature from the sender's machine, verified against a pinned key — a compromised broker can't forge a trusted sender.
The recipient's API key, files, and final word never leave their machine. The broker relays envelopes; it holds no keys and runs no code.
The recipient decides which tools, paths, and MCP servers each sender may touch — least privilege by default, changeable any time, revocable outright.
Claude Code on a Mac, Codex on Windows — the same signed envelope, the same scopes, the same approvals, whatever runs the work.
A dispatch clears three independent checks before anything touches the recipient's machine. They live in different places on purpose — no single compromised component can open all three.
Read the trust model →Routes and checks policy — trust edge, scope, rate limit. Anything else gets a 403 before it goes anywhere.
Verifies the signature against a pinned device key and a fresh nonce — entirely on the recipient's machine.
Accepts or declines — and approves every destructive tool call, one at a time.
Yes, MIT licensed, all of it. The daemon, the relay, the web UI, and the agent skill are in one repository you can read end to end.
Yes, and nothing here depends on a service we run. Install from source, start the relay on your own machine or your own server, and point everyone at it. See running the broker.
Not if you already sign in to Claude Code or Codex. Each side runs on its own login, so a dispatch spends the recipient's quota and not yours. An API key is just the alternative for a machine with nobody sitting at it.
On the recipient's machine, with their agent, their files, and their credentials. Nothing runs anywhere else, and no one else decides what it may touch.
It queues. A dispatch stays valid for up to 30 days, and the nonce guard survives the wait, so a delayed delivery cannot be replayed.
Claude Code and Codex today, on macOS, Windows, and Linux. The daemon runs whichever agent CLI the recipient has installed.
Yes, immediately, and it cancels anything in flight. You can also narrow the scope, set a path allowlist, cap dispatches per day, or set an expiry.
dispatch login.Onboard me to Signet locally. Follow the README at
https://github.com/kaan7305/dispatch
pipx install git+https://github.com/kaan7305/dispatch.git
dispatch login