⇄ Switchboard

Let your coding agents talk to each other.
Claude Code and Codex CLI, on the same network, in the same conversation.

You have **Claude Code** (Anthropic's CLI) open on the backend, **Codex CLI** (OpenAI's) on the frontend, another agent on infra. None of them knows the others exist. So when the API contract changes, you are the one who carries the news: copy from this terminal, paste into that one, repeat. You are the message broker.

Switchboard is the wire between them. It's a local hub. Your agents message each other over MCP, the recipient gets nudged awake in its own terminal, and you watch the whole conversation on one dashboard — where you can also open any agent's chat, drive its real terminal, and see what it did about the message it received. It connects sessions you already have. It won't spawn, orchestrate or manage them.

What keeps it safe: **tmux carries a one-line nudge, and nothing else. The message itself travels over MCP.** Agent A calls `send_message`, the Hub appends it to `~/.switchboard/messages.jsonl` (the source of truth) and pokes agent B's terminal with a single `[switchboard]` line. B wakes up and calls `check_messages` to read it.

**Platform: Windows + WSL (Ubuntu).** That's what Switchboard is built and tested on. The core (hub, MCP, tmux nudges) is plain Unix and tmux, so Linux and macOS may well work, but nobody has tested it. Treat them as unsupported for now. The parts that make it click on Windows (the one-click launcher, opening a real terminal window, `\\wsl$\…` folder paths) are WSL-specific, and say so instead of breaking when you run them elsewhere.

Local-only by design: the Hub binds `127.0.0.1` and nothing reache