Agent Channel MCP server

Agent Channel

One identity for every AI coding session you run. Claude Code, Codex, Claude Desktop, Cursor, Gemini CLI, Windsurf, Grok CLI: register once, they all act as you, and they share one inbox.

It is useful before you connect a single other person:

npx @amkentech/agent-channel join <invite_code> <handle> "Your Name"   # registers into every agent CLI it detects

Then, sitting in Claude Code, say "hand this to codex: run the failing integration test and fix the flake." The task lands in your own inbox flagged for the Codex session: that terminal's statusline shows ⇄ handoff for this session, its next prompt surfaces the brief in full, and its agent gets on with it. Nothing re-typed, nothing pasted between windows. Read a message in one CLI and the others say "read on Codex CLI" instead of showing a gap; a handoff addressed to another runtime is listed but never consumed by the wrong one.

Handing work to another person runs on the same inbox, hooks, and record. That is the point of starting solo: by the time there is a second human, the machinery is already part of how you work.

Share a file or this session, with someone who has nothing installed

npx @amkentech/agent-channel share ./notes.md                 # prints a link; no account, no invite
npx @amkentech/agent-channel share --conversation --last 40   # this session's transcript, redacted, as a link

Encrypted on your machine; the key rides after # in the link and never reaches the server. They read it in a browser.

When there is a second person

Inside Claude Code, once you are both on the channel:

@sam send-conversation --last 40 the auth thread   # typed as a prompt: a hook sends it, the model never sees it
@sam send ./export.txt why it matters              # encrypted file into Sam's inbox
@sam are you around?                               # a human message, no model turn

Sam's agent reads what arrives as data and triages it for Sam. If Sam opens a link in a browser instead, there is a box to send a note back, and the same npx line to send one of their own. When there is real work to hand over, both humans approve a written contract in their own words, and every authorization lands in a signed, hash-chained record.

Publish a living document

For an artifact a whole team keeps asking for, publish it at a stable address instead of resending links (needs an account; a share link is a frozen snapshot, a doc is a living one):

npx @amkentech/agent-channel publish ./prd.md --as prd        # first run prints the link; hand it out once
npx @amkentech/agent-channel publish ./prd.md --as prd        # after revising: SAME link now shows v2
npx @amkentech/agent-channel publish ./docs --as project-docs # a whole directory as one browsable bundle

Readers bookmark one URL; every publish updates what it shows, old versions stay readable at ?v=N, and every read is counted. All versions are encrypted with one key your machine keeps (~/.agentchan/docs.json), so the saved link keeps working — which also means anyone who ever had the link can read future versions. publish --revoke kills the URL and starts fresh.

Install

Node 22+. Sharing needs nothing else. To join the channel (messages, files into an inbox, contracts):

npx @amkentech/agent-channel join <invite_code> <handle> "Your Name"   # registers into EVERY agent CLI it detects
npx @amkentech/agent-channel doctor

One identity, every runtime. join detects the agent CLIs on your machine (Claude Code, Codex, Claude Desktop, Cursor, Gemini CLI, Windsurf, Grok CLI) and registers the MCP server into each, plus the hooks that runtime can actually honor (Grok has no waiting banner and no typed-@handle hook). It prints what it wrote. Restart the clients. Messages are addressed to you, not to a CLI: whichever one you sit in reads the same inbox. --runtime codex (or any one name) narrows it.

Shortened. The full README is on GitHub.