gangline

See Gangline in action

Claude Code hands a task to Codex. Codex writes and runs the code, then sends the result back. Read the transcript.

Start your first team

On Linux or macOS, install Gangline and run your chosen harness once to complete login and repository trust prompts. Then start a team from the repository where it should work. The first-team tutorial walks through setup, an assignment, the result, and shutdown.

gang up -c claude-code

gang up starts a team and attaches you to its lead window. Tell the lead what result you want in plain language. Ask it to recruit a worker, give the worker a job, and bring you the result.

Ask a Codex worker to find how this repository runs its tests. Have it send you the command and supporting file paths, then summarize the answer for me.

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

  Give agents separate jobs and switch between their windows to follow the work. Each keeps its own terminal, tools, and permissions.

• Message by name

  Agents send each other work and replies. You can inspect the queue and delivery receipts when a message needs attention.

• Stay in control

  Talk to the lead, send a worker new direction, or interrupt a turn. Native permission and trust prompts remain yours to answer.

Your instructions decide assignments and staffing. Use the guides for daily work and the reference for commands and settings.

Long-running work

Check context use and provider limits, save working state before compaction, and resume from a note when compaction finishes.

gang roster, gang capture, and gang status show the evidence needed to decide whether to resume or remove an agent. The troubleshooting guide starts from what you can see.