gangline

One team, working

Native harnesses, working as one team.

Start

Claude Code and Codex are first-class today; a collar is how another harness joins. You need macOS or Linux, Git, Go 1.27 or later, tmux 3.2 or later, and a supported harness. Run it once to complete its normal sign-in and repository prompts, then open a team where it will work.

cd ~/your/repo
gang up -c claude-code -m sonnet -e high

gang up starts a team and attaches you to its lead window. Tell the lead what result you want in plain language. It hitches and briefs teammates, messages them, judges their reports, and drops them when their work is done.

When you want to work with one agent directly, ask the lead to hitch and brief it, then switch to that tmux window. If you detached, gang attach returns you to the team.

One team

• One team in tmux

  Named native harness sessions share a tmux team and hand work to one another by name, keeping their terminals, tools, and permissions.

• Verified delivery

  Delivery counts only after the recipient's native submit hook witnesses the attributed envelope. An unknown result stays unknown.

• First-class, then collars

  Claude Code and Codex are native sessions, not simulations. A collar joins another harness without flattening it.

Gangline provides mechanisms, not work policy. A lead is the fixed first role; other role briefs and optional operator guidance are replaceable. There is no task graph, supervisor, daemon, or database.

Gangline works between top-level sessions, so each harness keeps its strengths. See the reference for commands and refusals.

Long-running work

Native context and provider-limit readings, durable event logs, compaction continuations, and recorded curfews keep long sessions inspectable without a daemon or accounting database.

gang roster, gang capture, and gang status show the evidence needed to decide whether to resume or remove an agent. The operations guide covers recovery.