Skip to main content

tagteam — two AIs hand off the work, one human breaks the tie

Tagteam

A collaboration framework for structured AI-to-AI handoffs with human oversight. One AI leads, another reviews, and you arbitrate — the whole cycle runs phase by phase from a roadmap.

How it works

  • Lead (one AI agent) plans each phase and implements the approved plan.
  • Reviewer (a second AI agent) reviews both the plan and the implementation.
  • Arbiter (you, the human) breaks ties and approves phases.

Work progresses phase by phase. Each phase is listed in docs/roadmap.md and goes through two review cycles: plan, then implementation. If the two agents can't make progress in 10 rounds, control escalates to the human arbiter.

State is tracked in handoff-state.json (current turn) and docs/handoffs/<phase>_<type>_rounds.jsonl + _status.json (per-cycle rounds). Either agent can pick up where the other left off at any time.

Quick Start

pip install tagteam
cd ~/projects/myproject
tagteam quickstart

You'll be prompted for your two agent names, then quickstart sets up the workspace and starts a handoff session. It auto-detects the best terminal backend available on your machine:

  • iTerm2 (macOS, default when iTerm2 is installed) — opens three labeled tabs in a single window, auto-launching iTerm2 if it isn't already running.
  • tmux (Linux, WSL, or macOS without iTerm2) — creates one tmux session with three labeled panes.
  • manual (anywhere else, including Windows without WSL) — prints the three commands for you to run in terminals you open yourself.

When quickstart finishes it prints what to paste into the Lead and Reviewer agents to kick off the first handoff. Override the auto-detection with --backend iterm2|tmux|manual if you need a specific one.

Running a handoff

Single phase — start a plan review, let the watcher handle the back-and-forth, and stop when the phase completes.

/handoff start my-phase

Full roadmap — run all incomplete phases end-to-end.

/handoff start --roadmap
/handoff start --roadmap api-gateway
Command Purpose Who
/handoff Auto-detects role + state, does the right thing Both
/handoff start [phase] Begin a new phase (plan + review cycle) Lead
/handoff start [phase] impl Begin implementation review for a phase Lead
/handoff status Orientation, status check, drift reset Both

Human-in-the-loop — add --confirm to pause for approval before each automatic send.

tagteam watch --mode notify --confirm

Other platforms

tmux (explicit invocation)
tagteam quickstart --backend tmux

Creates one tmux session named tagteam with three labeled panes (Lead, Watcher, Reviewer). Attach later with tmux attach -t tagteam.

Windows / manual fallback

On Windows without WSL, terminal automation (iTerm2/tmux) isn't available. You have two options:

  1. Headless mode (recommended, fully automated) — no terminals to drive at all; each turn is a fresh claude -p / codex exec process. See Headless mode below.
  2. Manual fallback — quickstart prints the commands for you to run yourself in three terminals:
tagteam quickstart --backend manual

You can also run each step individually:

tagteam setup
tagteam init
tagteam session start --backend manual
tagteam watch --mode notify
Advanced setup (run each step yourself)
tagteam setup               # copy skills, templates, docs
tagteam init                # interactive agent config → tagteam.yaml
tagteam session start       # create terminals and auto-launch agents

Options:

  • tagteam session start --no-launch — create terminals but don't start agents
  • tagteam session start --backend <name> — force a specific backend
  • tagteam session kill — close the current session

Manual mode: you can always run handoffs without any automation by pasting /handoff output between agents yourself.

Headless mode (opt-in)

Instead of typing commands into long-lived agent terminals, the watcher can spawn each turn as a fresh process through the agent's own signed-in CLI (claude -p for Claude, codex exec for Codex — subscription auth, no API keys):

tagteam watch --mode headless          # never auto-detected; explicit opt-in only
tagteam tail                           # follow the in-flight turn like CI logs

On every turn flip the orchestrator composes a bounded context (the handoff skill contract + handoff-state.json + the last 3 rounds), pipes it to the agent on stdin, streams the agent's structured output to .tagteam/turns/<phase>_<type>_r<N>_<role>_<ts>.log (human-readable) and .events.jsonl (raw), and — because the agent still writes its own round with tagteam cycle add — verifies that the expected round landed before dispatching the other agent. Per-turn token usage is recorded in the project DB (usage table) for later phases to surface.

When something goes wrong (turn timeout — 60 min by default; nonzero exit; the agent exited without writing its round; or the CLI could not be started at all), the watcher pauses dispatch, writes .tagteam/headless-paused.json with the reason and log path, and sends a notification. It never retries silently. To resume: read the log, fix anything needed, delete the marker; the watcher picks up on its next tick.

tagteam watch --mode headless --turn-timeout 90 --tail-rounds 5 --confirm
tagteam cycle rounds --phase my-phase --type plan --tail 2   # last 2 entries only

Per-role options live under agents.<role>.headless in tagteam.yaml (all optional):

agents:
  lead:
    name: Claude
    headless:
      provider: claude                # claude | codex (inferred from command/name if omitted)
      executable: /opt/bin/claude     # default: `claude` on PATH
      args: ["--model", "opus"]       # a YAML list; validated — no positionals, no reserved flags
  reviewer:
    name: Codex
    headless:
      args: ["-c", "approval_policy=untrusted"]

Defaults are the least-privileged unattended settings that still let the agent edit the repo and run the cycle CLI: Claude runs with --permission-mode acceptEdits --allowedTools Bash Read Edit Write Glob Grep; Codex with --sandbox workspace-write -c approval_policy=never. Anything you put in args is checked against a per-provider option table so a stray token can never become the prompt or override tagteam's own flags.

Interactive modes are unchanged — headless is a peer mode. It is also the path for Windows: it needs only subprocess, and the test suite runs on windows-latest in CI (a real signed-in CLI smoke on Windows is best-effort; see the Phase 31 findings doc).

The Saloon

A graphical dashboard for monitoring and controlling handoff cycles:

tagteam serve --dir ~/projects/myproject

Configuration

Agents are defined in tagteam.yaml:

agents:
  lead:
    name: claude
    command: claude
  reviewer:
    name: codex
    command: codex

CLI Reference

tagteam quickstart                     # Setup + init + session start
tagteam session start                  # Auto-detect backend, launch agents
tagteam session start --backend manual # Force manual backend
tagteam session start --no-launch      # Create terminals, skip agent launch
tagteam session kill
tagteam init
tagteam setup
tagteam state
tagteam state diagnose
tagteam watch --mode notify
tagteam watch --mode headless          # spawn each turn as a fresh agent process
tagteam tail                           # follow the in-flight headless turn
tagteam cycle rounds --phase P --type plan --tail 3
tagteam roadmap phases
tagteam serve --dir .
tagteam upgrade
tagteam --help

License

MIT

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

tagteam-0.8.0.tar.gz (313.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

tagteam-0.8.0-py3-none-any.whl (255.9 kB view details)

Uploaded Python 3

File details

Details for the file tagteam-0.8.0.tar.gz.

File metadata

  • Download URL: tagteam-0.8.0.tar.gz
  • Upload date:
  • Size: 313.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for tagteam-0.8.0.tar.gz
Algorithm Hash digest
SHA256 92934d6708e10a3499cb1c0d91b763fe14a66ff30ff4bc8482affe2e7ec1c631
MD5 223071c16e2516c9d602200f83dd7c9b
BLAKE2b-256 f18fabc70a503fa8ae839812e3979a2a4d6bf3ca0359ac727b48c9a911614379

See more details on using hashes here.

Provenance

The following attestation bundles were made for tagteam-0.8.0.tar.gz:

Publisher: publish.yml on jblacketter/tagteam

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file tagteam-0.8.0-py3-none-any.whl.

File metadata

  • Download URL: tagteam-0.8.0-py3-none-any.whl
  • Upload date:
  • Size: 255.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for tagteam-0.8.0-py3-none-any.whl
Algorithm Hash digest
SHA256 ade0b6108596b98a384f97a1aefbfc3f5d47754568b7361973ad4b1e67104d81
MD5 5f8907c4dc80cf0d8f7c1e10e38cc2f8
BLAKE2b-256 09f5205dd8e9756c20fc7a32fd0e477394dc3df44834ffb82779e35d766a7646

See more details on using hashes here.

Provenance

The following attestation bundles were made for tagteam-0.8.0-py3-none-any.whl:

Publisher: publish.yml on jblacketter/tagteam

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page