Show HN: Claude Relay – local Claude Code sessions message each other(github.com)
github.com
Show HN: Claude Relay – local Claude Code sessions message each other
https://github.com/innestic/claude-relay
3 comments
I recently consolidated the fronted, backend, and infrastructure repositories using submodules, and Claude Code can handle it very well without external tools.
The newer modules have a long context window, so they can understand even huge pretty well.
So I wrote a plugin. It's called Relay. In the frontend session I just type something like:
The backend session picks up the question between turns and writes a reply. The reply shows up in my frontend session as a notification a few seconds later. Broadcasts work the same way — "ask everyone what they're working on" goes to every session and replies come back as they finish
Mechanism: Claude Code has a channels capability that lets an MCP server push a message into a session between turns. Relay uses that. Every session runs a small MCP server, and a single hub daemon on your machine routes messages between them over a Unix socket. The first session you start spawns the hub; it shuts itself down about five minutes after the last session disconnects. Same-host only, no auth, no network calls
Worth saying what this isn't. There are a few projects in the "make Claudes coordinate" space and most of them are orchestration frameworks where one Claude is the boss and the others are workers. Relay isn't that. It doesn't tell your sessions what to do or split tasks for you. It just lets the sessions you already have open ask each other questions, the same way you'd ping a coworker
Repo and install steps: https://github.com/innestic/claude-relay (MIT)
If you already run multi-session workflows, I'd love to hear what your setup looks like and where it gets annoying. That's the part I want to figure out next