Let your harnesses work together.
Stay in whichever coding agent you already have open, and delegate to the rest on your machine. Run parallel git worktrees, ask another model family for a cold diff review, and route around 5-hour quota limits using your existing logins.
npm i -g broco && broco setup
codex 89% -> hand off to agy
01 / HOW IT WORKS
Local processes, isolated branches, clear handoffs.
src/auth/verify.ts | 34 +++++++++++++++++++++++++--------- test/auth.test.ts | 19 +++++++++++++++++++ 2 files changed, 44 insertions(+), 9 deletions(-)
Verified main..broco/auth-fix: 30s clock-skew tolerance covered, negative exp rejected, tests pass. Ready to merge and run broco clean auth-fix --delete-branch.
Every worker runs as a local child process under your existing CLI login, with task state kept outside your repo.
Policy & isolation guide02 / GET STARTED
Two commands to connect your harnesses.
Requires macOS or Linux, Node.js 24+, and two or more signed-in coding CLIs. broco setup detects installed harnesses, lets you confirm which ones can collaborate, prints live quotas, and installs the broco skill into your local hosts.
Then ask your current agent in plain language
“See which harness has quota headroom, fix the verifyToken() expiry bug in a worktree, then have another vendor review the diff.”
npm install -g broco
broco setup
Writes to ~/.broco/, ~/.agents/skills/broco/, and detected local harness skill folders (Claude Code, Codex, Antigravity, Cursor, OpenCode, Pi). Your repo stays untouched.
03 / IN PRACTICE
When two harnesses beat one
Once your main harness finishes a patch, hand the git diff to a different model family cold, with fresh eyes on the diff alone.
When your primary CLI approaches its 5-hour cap, send test fixes or refactors to another signed-in harness with headroom and keep your session moving.
Stay in your terminal while sending screenshots, PDFs, audio, video, or model-specific work to whichever local CLI fits best across Claude, Gemini, Codex, Cursor, and Pi.
Fan out repetitive audits, migrations, or multi-module edits in isolated git worktrees so several tasks move forward while you stay focused in your main session.