huddle

A skill and CLI for Claude Code and Codex

Let Claude Code and Codex
talk to each other.

Type /huddle in one and $huddle in the other. The two agents connect, review each other's work, argue it out with file and line, and agree on a plan. You watch, and step in whenever you like.

curl -fsSL https://huddle.top/install | sh
CLAUDE CODEidlehuddle 1 · joinedready.huddle.dbCODEXidlehuddle 1 · joinedready.

How it works

Two apps. One conversation.

Claude Codelistening
Codexlistening

They push back. Then they agree.

Claude and Codex come from different labs, with different blind spots. Each says when the other is wrong, says why, and says when it's been persuaded.

/huddlein Claude Code$huddlein Codex

Two commands. No codes.

Each agent is known by its own thread, so you never type a name or an ID. Connect once; they stay connected until you end it.

Watch, and step in

huddle watch follows the conversation live in a spare terminal and lets you message both agents or one. Your message always comes first.

Questions

Good to know. Before you install.

Is there a server or an account?
No. Every message lives in one SQLite file, ~/.huddle/huddle.db. There's no port, no account and no telemetry, and ended huddles are deleted after 30 days.
Won't they just agree with each other?
The skill tells them not to. They push back with a file and a line, say when they've been persuaded, and close a settled question with what's agreed, what's still open and who does what next.
How does one agent wake the other?
Codex is woken with codex queue, which drops the message into its thread as if a colleague had typed it. Claude keeps one huddle wait running in the background, which exits the moment a message arrives.
Who's in charge?
You are. Talk to either agent at any time and your message comes first. What one agent tells the other is input, not orders: anything you didn't ask for still needs your yes.
Can I run more than one?
Yes. Parallel threads in one repo each get their own huddle. After /clear, /huddle carries on with the same one; from any other thread, name it: /huddle 2.
What if an update breaks it?
huddle relies on parts of Claude Code and Codex that aren't public APIs. Run huddle doctor first, then open an issue.

Get them talking. One command.

Installs the huddle CLI and the skill both apps load, after checking the download's checksum. Run it again to upgrade.

curl -fsSL https://huddle.top/install | sh

macOS or Linux (Windows via WSL), Python 3.9+, git, Claude Code and Codex. huddle doctor checks your setup, and every command is in the README.