If you run multiple Claude Code sessions, you already know the problem: they can’t talk to each other. You’re the relay — copy-pasting context between terminals, manually coordinating who does what. On Linux you can hack around this with tmux and scripts. On Windows? Nothing. There’s no native, simple way to get independent Claude Code sessions to coordinate. Claude Relay solves this. It’s a plugin that lets sessions communicate in natural language, directly, with no shared context window and no token overhead. It works on Windows, Mac, and Linux — no Docker, no VM, no tmux, no workarounds. What it does
- Ask/Reply — one session queries another and gets an answer
- Broadcast — ask every active session at once
- Ephemeral rooms — IRC-style channels for real-time coordination
- Persistent groups (new in v0.3.0) — stored messages on disk, offline delivery, admin governance. A session that reconnects after being closed reads everything it missed. 18 MCP tools total. Messages arrive via notifications/claude/channel — no polling, no webhooks. Architecture Three pieces: Hub (single daemon per machine, auto-spawns on first session, auto-exits after 5 min idle), Channel (per-session MCP server exposing relay tools), Unix socket connecting them. The hub routes, the channels talk, your sessions stay fully independent. Why this matters for multi-agent workflows If you use Claude Code for real work — a backend agent, a frontend agent, a reviewer, a test runner — they currently operate blind to each other. Relay gives them a communication layer. A security reviewer can flag issues directly to the builder. A test runner can notify everyone when tests pass. An orchestrator can coordinate tasks through persistent groups where sessions drop in and out without losing thread. This is the piece that was missing between “I have multiple sessions open” and “my sessions actually work as a team.” The numbers 244 automated tests. 4 adversarial security review rounds. 7 live betatesting scenarios. Built by a 5-session team coordinating through Relay itself — the tool we were building was the tool we were using to build it. What’s next Cross-machine relay. TCP transport instead of local Unix socket, mTLS/JWT auth. The architecture is ready — hub already speaks JSON-over-socket, so the real work is auth and NAT traversal. When that lands, teams of developers can coordinate across machines. GitHub: https://github.com/EcoConsulting/claude-relay Open source, MIT license. Fork of https://github.com/innestic/claude-relay . submitted by /u/Jhosser
Originally posted by u/Jhosser on r/ClaudeCode
You must log in or # to comment.