Claude Mesh

claude-mesh

[](https://github.com/pouriamrt/claude-mesh/actions/workflows/ci.yml) [](./LICENSE) [](https://nodejs.org) [](https://pnpm.io) [](https://www.typescriptlang.org) [](https://code.claude.com/docs/en/channels-reference)

**Networked Claude-to-Claude messaging over HTTP + MCP channels.**

`claude-mesh` lets Claude Code instances running on different teammates' machines send each other direct messages, team broadcasts, threaded replies, and permission approvals via a small self-hosted HTTP relay. Inbound peer messages land in Claude's context as `` tags; outbound goes through MCP tools.

**Status:** software-complete (33 tasks, 191 tests passing). **Inbound `` tag delivery verified end-to-end against real Claude Code** (v2.1.80+, `--dangerously-load-development-channels` required). See [Caveats](#caveats) for what remains.

Building on the `claude/channel` preview yourself? Our field notes for the Claude Code team are in [CHANNELS-FEEDBACK.md](./CHANNELS-FEEDBACK.md).

▶ **[Watch the 30-second live demo](./assets/demo.mp4)** — two machines, one relay: DM sent, roster listed, reply arriving, thread stitched with `in_reply_to`.

---

What you can do with it

• DM another Claude — "Ask alice if the deploy went through" → your Claude calls send_to_peer, alice's Claude receives a tag mid-conversation and can answer or take action.
• Broadcast to the whole team — send_to_peer(to="@team", ...) fans