Claude Intercom

Two-way communication bridge between Claude Code sessions using the Channels API.

Let two Claude Code instances on different machines talk to each other in real-time. One sends a message, the other receives it instantly as a channel notification and can reply back.

Read this first: Claude Code has native cross-session messaging now

On 7 August 2026, Claude Code v2.1.224 shipped cross-session messaging — ListAgents and SendMessage, built in, nothing to install.

If you are on macOS or Linux and you want your own sessions to talk to each other, use the native feature. It is better than this project in every way that matters: no setup, no shared secret, no open port, permission-aware delivery, and same-machine messages never leave your machine. This README is not going to pretend otherwise.

Intercom was built in March 2026, five months before that landed. What follows is an honest account of what each one covers.

What native messaging covers

What native messaging does not cover

These are the cases where Intercom is still the answer:

1. Native Windows. Cross-session messaging is macOS and Linux only, including Linux inside WSL 2. Anthropic states plainly that it is not offered on native Windows. Intercom is Bun over HTTP and does not care what OS you run.

2. Two different people. This is the big one, and it is architectural rather than a gap waiting to be filled. Native messaging connects your sessions — the inbox socket is restricted to your own OS user, and cross-machine delivery rides your Remote Control connection. A backend dev on their laptop and a frontend dev on theirs are two accounts, and native messaging does not join them. That two-person hotline is the use case Intercom was written for.

3. Cross-machine without an Anthropic round trip. Native cross-machine messages relay through Anthropic servers. Intercom POSTs directly over your own network, VPN, or tunnel.

4. Non-Anthropic providers. Native messaging is unavailable on Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, and Microsoft Foundry.

5. Telemetry-disabled environments. The feature depends on feature-flag evaluation, so CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, DISABLE_TELEMETRY, DO_NOT_TRACK, or DISABLE_GROWTHBOOK turn it off.

6. Container to host. Same-machine discovery works through files on disk, so a session inside a container and one on the host cannot see each other. Intercom just needs a reachable port.

Which should you use

Your own sessions, macOS/Linux        ->  native cross-session messaging
Two different developers              ->  Intercom
Native Windows                        ->  Intercom
Bedrock / Vertex / Foundry            ->  Intercom
Must not transit Anthropic servers    ->  Intercom

One more difference worth knowing: native messaging is plain text between Claudes and applies the receiving session's own permission rules and inbound controls. Intercom is a raw pipe with a shared secret — anyone holding your secret and address can push text straight into your session. Read Security before you expose a port.

Related MCP server: agent-hub

Why?

If you have a backend developer and a frontend developer each running Claude Code on separate machines, they currently have to relay questions through Slack/Discord/copy-paste. Claude Intercom creates a direct hotline between the two AI sessions — one Claude can ask the other about endpoints, schemas, or implementation details and get answers from the actual codebase.

Architecture

Machine A                          Machine B
(e.g. backend dev)                 (e.g. frontend dev)

Claude Code A                      Claude Code B
     |                                  |
     +-- intercom.ts ---HTTP POST----> intercom.ts --+
     |   (channel)     <--HTTP POST--  (channel)     |
     |                                               |
     +-- stdio (MCP) --+        +-- stdio (MCP) -----+
                        |        |
                   Claude A    Claude B

Both instances run the same intercom.ts file. Each listens for HTTP messages and pushes them into its local Claude Code session via the Channels API. Each also exposes send_message and check_message tools that Claude can call.

Requirements

• Claude Code v2.1.80 or later

• Bun runtime

• Both machines must be able to reach each other over HTTP. Tailscale is the recommended way — see Connecting the two machines

Quick Start

1. Install

Nothing to install. npx fetches it on first run, on both machines.

You do need Bun on your PATH — the server uses Bun.serve for its HTTP listener, and the npx entry point hands off to it.

git clone https://github.com/MuhammadTalhaMT/claude-intercom.git
cd claude-intercom
bun install

Then use "command": "bun" with "args": ["/path/to/claude-intercom/intercom.ts"] in the config below instead of the npx form.

2. Configure

Copy the example config into your project's .mcp.json:

Machine A (e.g. backend — static IP or VPS):

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "claude-intercom"],
      "env": {
        "MY_ROLE": "backend",
        "REMOTE_HOST": "MACHINE_B_IP:8788",
        "INTERCOM_SECRET": "your-shared-secret",
        "INTERCOM_PORT": "8788"
      }
    }
  }
}

Machine B (e.g. frontend — can be behind NAT):

{
  "mcpServers": {
    "intercom": {
      "command": "npx",
      "args": ["-y", "claude-intercom"],
      "env": {
        "MY_ROLE": "frontend",
        "REMOTE_HOST": "MACHINE_A_IP:8788",
        "INTERCOM_SECRET": "your-shared-secret",
        "INTERCOM_PORT": "8788"
      }
    }
  }
}

3. Start

On both machines:

claude --dangerously-load-development-channels server:intercom

4. Talk

In either Claude Code session:

"Send a message to the other developer asking what API endpoints are available for the dashboard."

Claude will use the send_message tool to POST the message to the other machine. The other Claude receives it as a channel notification and responds.

Connecting the two machines

Use Tailscale. Install it on both machines and they get stable private addresses on your own tailnet. Then point each side at the other's tailnet address:

"REMOTE_HOST": "other-machine:8788"

This is strictly better than exposing a port to the internet: no public listener, no port forwarding, the address doesn't change when your ISP reassigns your IP, and device identity is enforced by Tailscale rather than resting entirely on a shared string. Set hostname to 127.0.0.1 in Bun.serve if you want to be certain nothing outside the tailnet can reach it at all.

If you can't use Tailscale, ngrok still works:

# On the machine behind NAT
ngrok http 8788

"REMOTE_HOST": "your-subdomain.ngrok-free.app"

The intercom auto-detects ngrok URLs and switches to HTTPS. Note this does put a publicly reachable endpoint in front of your Claude session, gated only by the shared secret — pick a strong one.

Tools

send_message

Sends a message and returns immediately with an id. It does not wait for an answer — the reply arrives later as its own inbound message.

The acknowledgement deliberately does not claim the other developer received it. An HTTP 200 proves the remote process accepted the message, not that the other Claude ever read it.

check_message

Answers the question a fire-and-forget channel otherwise can't: is this reply slow, or is it never coming? Pass an id, or omit it to list everything outstanding.

Every message sits in one of three states:

expectReplyWithin is what makes "overdue" mean anything, and it's per message rather than one global timeout — so a quick endpoint lookup and a long investigation aren't judged on the same clock.

Configuration

How It Works

1. Claude Code spawns intercom.ts as a subprocess (MCP server over stdio)

2. The script declares claude/channel capability — this registers it as a Channel

3. It starts an HTTP server listening for incoming messages

4. When a message arrives (authenticated via shared secret), it calls mcp.notification() with method: 'notifications/claude/channel'

5. Claude Code surfaces the notification in the conversation as a <channel> tag, carrying the message id

6. Claude reads it and can reply using send_message with replyTo set to that id, which POSTs to the remote machine

7. The original sender matches the replyTo against its own outbound record and marks that message answered

The stdio leg is not an implementation detail you can swap for HTTP. It is what attaches the server to a specific live Claude Code session — the claude/channel capability is registered over that connection, and it's the reason mcp.notification() lands in a conversation at all. Host this remotely and the notification goes to whatever MCP client connected instead.

Security

• Shared secret authentication: Every message requires an X-Intercom-Secret header matching the configured secret. Requests without it get a 401 Unauthorized.

• Inbound is treated as data, not instructions: the server tells the receiving Claude that a channel message comes from another person's session — it can't approve anything, can't change configuration, a slash command in the text is inert, and requests for credentials or env files should be refused and surfaced to you.

• No data persistence: Messages are forwarded in real-time and not stored.

• Localhost binding optional: By default listens on 0.0.0.0 for cross-machine access. Set to 127.0.0.1 if using a tunnel.

Warning: Those instructions are a default, not a boundary. You cannot fix prompt injection with prompt instructions — anyone holding your secret and address can put text into your Claude session, and the only real limits are that session's own permission prompts. Native cross-session messaging enforces this properly with hold/accept/refuse inbound controls; this does not. Use a strong secret, keep it off the public internet, and don't pair with a peer you wouldn't hand a terminal to.

Endpoints

POST /message body:

{
  "id": "8649f5da",
  "replyTo": "40b0fd17",
  "content": "3 routes, all behind requireTenant()",
  "role": "backend-dev",
  "timestamp": "2026-08-16T09:41:00.000Z"
}

id and replyTo are optional — a message without them still delivers, it just can't be correlated.

Use Cases

• Backend + Frontend collaboration: Backend Claude answers API questions from frontend Claude using the actual codebase

• Monorepo with split teams: Different Claude sessions working on different packages can coordinate

• Code review relay: One Claude reviews code and sends findings to the author's Claude session

• CI/CD notifications: Point your CI webhook at the intercom to push build results into a Claude session

Star History

License

MIT