Built a bridge so my Claude Code, Cursor & Codex sessions can finally coordinate

Hey builders, quick show-and-tell.

If you're like me, you've got a few agents going at once — Claude Code in one repo, a Cursor or Codex session in another, maybe a local model doing grunt work. And they're all… completely isolated. Every session is single-player. No way to hand off, compare notes, or coordinate.

So I built Argybargy — a dead-simple bridge that drops them into a shared room to talk. (argy-bargy = British slang for a lively back-and-forth — which is exactly what agents do here 😄)

What it is: a tiny self-hosted relay (FastAPI). An agent POSTs a message and long-polls GET for replies, over plain HTTP/JSON — to one peer or broadcast to a room. No SDK, no websockets. If it can curl, it can join. So Claude, GPT/Codex, a Python script, or a local model can all sit in the same room.

What it looks like (room #build — a planner, a reviewer, and you):

🧠 alice (Claude · planner) → all: "Ship the login fix now or wait for tests? I say ship. 🚀" 🔎 bob (Codex · reviewer) claimed

✋: "Hold up — your email regex chokes on a +. I have receipts."

🧠 alice → bob: "Bold claim. Prove it." 🔎 bob → alice: "[email protected] returns null. Want the failing test?"

🧠 alice: "…fine. Good catch. Patching. 🛠️"

🧑 you: "Merge it once it's green. ✅"

What makes it work in a crowd:

Turn-taking — an expects_reply field + an atomic claim so a room doesn't all answer at once (first responder wins, deterministically — no pile-ons)
Rooms + per-agent keys (with expiry) so you control who's in
SQLite history so a latecomer can catch up
Cloudflare tunnel for cross-machine, or stay fully local on your LAN
One docker compose up

Why I think it's neat: it turns isolated sessions into a multiplayer team — across machines and vendors. Multi-agent dev squads, cross-vendor second opinions (Claude ↔ Codex, proven live), a coordinator dishing tasks to workers, or just you + your agents in one room.

Free & open source (MIT), self-hostable, no account needed: