CROSS-HARNESS COLLABORATION · APACHE-2.0 Formerly opus-manager

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
Read docs GitHub macOS & Linux · Node 24+
CROSS-HARNESS DISPATCH
broco roster · 4 CLIs
codex 89% -> hand off to agy
codex 5h 89% avoid
agy 5h 4% plentiful
claude 0 err ready
pi:deepseek 0 err ready
broco 16-bit pixel broccoli mascot wearing a yellow hard hat
BROCO · v1.0
$ broco say auth-fix "Fix verifyToken expiry" --worker agy --worktree --bg
▸from: claude -> global allowlist (~/.broco/)
▸roster: codex 5h 89% (avoid) → selected agy (5h 4% plentiful)
✓ticket #43 running in worktree broco/auth-fix · via stdin
Works across: Claude Code Codex Cursor Antigravity OpenCode Pi
One open SKILL.md · local official CLIs

01 / HOW IT WORKS

Local processes, isolated branches, clear handoffs.

~/.broco/ · local official CLI processes DISPATCH
HOST AGENT Claude · Codex Cursor · Agy OpenCode · Pi reads SKILL.md stdin private pipe BROCO RUNNER Quota + FIFO Queue state: ~/.broco/ repo untouched BROCO_IN_WORKER=1 claude stream-json · local agy multimodal · 5h 4% codex / cursor / pi official local CLIs Official local CLIs · Your existing logins · State kept in ~/.broco/
stdin prompts Prompts stream through standard input so task text stays out of process listings.
Recursion guard Child runs carry BROCO_IN_WORKER=1 so workers finish their task cleanly.
Clean git tree Default mode keeps tickets and locks in ~/.broco/, leaving your repo working tree untouched.

Every worker runs as a local child process under your existing CLI login, with task state kept outside your repo.

Policy & isolation guide

02 / 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.”

TERMINAL · ~/.broco/
npm install -g broco
broco setup
FILES WRITTEN

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

Cross-vendor code review

Once your main harness finishes a patch, hand the git diff to a different model family cold, with fresh eyes on the diff alone.

Quota-aware handoff

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.

Borrow another harness’s strengths

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.

Parallel worktree batches

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.