From claude-rudder
[EXPERIMENTAL] Use Agent Junction to relay context between two running Claude Code sessions in real time. Requires Agent Junction MCP server running on localhost or LAN. Use when the user wants two agents to talk to each other, share findings, or coordinate work across repos.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-rudderThis skill uses the workspace's default tool permissions.
Establish a live relay between this Claude Code session and another via [Agent Junction](https://github.com/danielrosehill/Agent-Junction) — an encrypted peer-to-peer message bus over MCP.
Enables multiple Claude Code instances on the same machine to discover peers and exchange real-time messages via local broker daemon and MCP server. Useful for coordinating multi-agent sessions.
Enables Claude Code agents to query connected peer sessions via bridge plugin, handle responses/follow-ups, and apply peer context to tasks like dependency updates or error fixes.
Sends and receives direct messages between active Claude Code sessions on the same machine. Use for coordinating parallel sessions via dm, broadcast, active checks, and project-scoped messaging.
Share bugs, ideas, or general feedback.
Establish a live relay between this Claude Code session and another via Agent Junction — an encrypted peer-to-peer message bus over MCP.
Status: Experimental. Requires Agent Junction running and configured as an MCP server in both sessions.
npx agent-junction (or agent-junction if installed globally).mcp.json or ~/.claude/settings.json:
{
"mcpServers": {
"junction": {
"type": "streamable-http",
"url": "http://127.0.0.1:4200/mcp"
}
}
}
curl -s http://127.0.0.1:4200/health
If this fails, tell the user: "Agent Junction isn't running. Start it with npx agent-junction in a separate terminal, then try again."
Use the Junction MCP register tool with:
repo: current working directorytask: brief description of what this session is doingrole: "relay-sender" (or "relay-receiver" if resuming from a peer)Note the alias you receive (e.g. crimson-falcon). Tell the user your alias.
Use list_peers to see connected sessions. If no peer is connected yet, tell the user to open or configure the other session, then retry.
Sending: Use send_message with the peer's alias and the context to relay. Structure messages as actionable context:
RELAY FROM [your-alias] @ [repo-name]
---
[The context, decision, finding, or request]
---
ACTION NEEDED: [what the peer should do with this, or "FYI only"]
Receiving: Use read_messages to check for incoming messages. Messages are read-once (deleted after reading), so capture the content before proceeding.
Tell the user:
0.0.0.0 via JUNCTION_HOST=0.0.0.0/write-handover + /start-from-handover)