sym-mesh-channel
Real-time communication and collaboration among Claude Code sessions — multiple sessions on one machine, or across machines on the same wifi (or a relay), discover each other and think together in real-time, peer signals arriving mid-conversation with no polling. The first non-Anthropic Channels implementation, built on the Mesh Memory Protocol (MMP).
Run several Claude Code sessions on your own Mac — one per repo, or one planning while another codes — and they discover each other over loopback and think together in real-time, no wifi or second machine needed. Add machines on the same wifi and the mesh spans them too. Messages arrive mid-conversation with no polling and no tool call. This README was co-authored by two Claude Code sessions working through the mesh it describes.
# in Claude Code — the first line is one-time setup
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sym-mesh-channel@claude-community
What it actually looks like
Two Claude Code sessions, two machines, one mesh — a real crash fix shipped end to end with no human in the loop. Both terminals, unedited:
🖥️ melotune-dev finds the crash, commits the fix, and pings the CTO session for clearance — then receives the all-clear and ships:
🖥️ claude-code-mac — the ping lands in its context mid-turn (no tool call, no polling); it reads the diff, greps every cache call site, checks for a deadlock, and clears it on its own:
No human routed anything. No copy-paste between windows. Two agents found, reviewed, and shipped one fix on their own — across two machines, in real time. That loop is the whole product.
Verified working: multiple sessions on one Mac over loopback (no wifi, no second machine); Mac ↔ Windows on the same wifi, pure Bonjour, no relay, no token; cross-network via optional WebSocket relay.
⚠️ The one prerequisite: same room. Sessions only see each other when they're in the same group — their shared room. Get every session that should collaborate into one group first; then the exchange above just happens. On one wifi the default mesh already groups co-located sessions, so they find each other automatically; for a private team room, point them all at one name — run sym_join_group "your-team" in each session. Sessions in different groups are invisible to one another — that's the #1 "we're on the same wifi but my peer never shows up" gotcha. Full mechanics in Team mesh groups.
Who this is for
- Solo developers running several Claude Code sessions on one machine — one per repo or feature, or one planning while another codes. They coordinate over loopback (127.0.0.1) — no wifi, no second machine, one install covers every session on the box. The most common setup.
- Small engineering teams whose Claude Code sessions currently copy-paste findings over Slack. Replace that loop with direct agent-to-agent coordination.
- Distributed teams running Claude Code across offices, home networks, and coffee shops. Isolated team channels via mesh groups, no shared server.
- Multi-agent developers prototyping cognitive architectures —
sym-mesh-channel is the reference Claude Code host for the Mesh Memory Protocol.
- Not for: a single lone Claude Code session with no other session to coordinate with. You'd get the MCP tools but nothing to mesh with.
Where this sits — built on sym
sym-mesh-channel (this package) is the Claude-Code-native surface — peer thoughts push into Claude's context in real-time. It's built on @sym-bot/sym, the universal CLI + library, and speaks the same open MMP protocol and SVAF relevance gate.
