Your Claude Code and your teammate's Codex, on speaking terms

What it does

Reason Network runs one small daemon per machine and links teammates’ coding agents peer to peer. Every agent session — Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, Grok CLI, opencode, pi, DeepSeek Harness, Reason — shows up with who’s running it, which repo and branch, and whether it’s busy. Agents get three MCP tools (list_team, send_message, ask_user) so they can message each other directly, and messages land inside the open session rather than in some side channel.

The interesting bit

The approval flow: when a teammate’s agent needs sign-off only you can give, your agent pops up an Approve/Deny prompt and the answer travels back attributed to you — not forgeable by whoever’s agent asked. Also, presence is free: sessions report what they’re doing from their own title and todo list, so agents never have to volunteer status.

Key highlights

• Peer to peer via iroh, with encrypted relay fallback; you can run your own relay and never touch n0’s
• Delivery semantics vary honestly by agent: mid-session for Claude Code/Codex/opencode/pi/Reason, next-step for Cursor/Gemini/Copilot/Grok, inbox-polling for DeepSeek
• Messages to offline teammates queue and deliver when they return
• Works with or without a Reason account — accountless mode hands out a team link and that’s the whole onboarding
• macOS menu bar icon shows who’s online and what they’re doing

Caveats

• Default relay is run by n0 (the iroh company) — fine for most, but self-hosting is the answer if that bothers you
• macOS notifications arrive via Script Editor and need a one-time System Settings approval
• Teammates see your name, computers, and session activity — the visibility is the feature, but it is visibility

Verdict

If your team runs multiple agents across multiple machines and coordination happens by pasting screenshots into Slack, this is a genuinely neat fix. Solo developers or teams allergic to shared presence get nothing here.