CrewCo

Staff a team of agents. Hand it the ticket.

CrewCo runs each task through a Team Lead, Developer, Tester and Code Reviewer, plus a UI/UX Designer when you want one. Every seat gets its own CLI, model and reasoning effort.

See how a task moves

Your crew

Fill or empty a seat, pick the CLI each one runs on, then send a task through. Seats here are a demo. The real lineup is confirmed per task.

  1. Team Lead

    Scopes the task with you in chat, writes the acceptance criteria and picks the lineup.

  2. UI/UX Designer

    Vacant. Switch it on to add this seat.

  3. Developer

    Implements the task in an isolated git worktree.

  4. Tester

    Writes and runs tests against the acceptance criteria.

  5. Code Reviewer

    Reads the diff for correctness, style and security.

Waiting for a task. Run one to watch it move through the seats above.

A task goes through a crew, not a single prompt.

Splitting the work across roles means the code is written by one agent, tested by another and reviewed by a third, each with a narrow job.

  1. 1

    Scope it in chat

    Describe the task. The Team Lead asks what's missing and turns it into acceptance criteria.

  2. 2

    Confirm the lineup

    Choose which seats work on this task, and which CLI, model and reasoning effort each one runs on.

  3. 3

    Run the fix rounds

    The Developer builds, the Tester checks the criteria, the Reviewer reads the diff. Findings go back to the Developer for up to three rounds.

  4. 4

    Take the result

    Work happens in an isolated git worktree, so your checkout stays untouched until you merge.

Delegate to agents from every CLI, and manage them in one place.

Claude Code, Codex CLI, GitHub Copilot CLI and Antigravity each have their own agents, sessions and logins. CrewCo sits above them: give it a task once, put each role on the CLI and model you want, and follow the whole job from one tool.

One task

“Add rate limiting to the upload endpoint”

CrewCo

  • Scopes and splits the work
  • Assigns each role to a CLI
  • Tracks every run on one board
  • Team LeadClaude Code
  • UI/UX DesignerAntigravity
  • DeveloperCodex CLI
  • TesterClaude Code
  • Code ReviewerCopilot CLI

Hand it off once

Describe the task in chat. The Team Lead scopes it and assigns the work to the other roles.

Mix CLIs freely

Claude Code can lead, Codex can build, Copilot can review. Each role runs on the CLI, model and effort you choose.

Run it from one place

Watch every run live on a single task board, resume a task, and check each CLI's health, from the web UI or the terminal.

It runs on your machine.

  • The app listens on 127.0.0.1, and nothing about your project leaves for a CrewCo server.
  • Team settings, project notes and task history are plain files in .crewco/ that you can commit.
  • Every task works in its own git worktree by default.
  • A web UI and a CLI share the same on-disk format, so you can start in one and continue in the other.
# open the web UI and the first-run wizard
crewco ui

# or skip the browser
crewco run "add rate limiting" --design

# check on it, pick it back up
crewco status
crewco resume

# check which CLIs are ready
crewco doctor

# start the app at login
crewco service install

One command to meet the crew.

The first-run wizard checks which of the four CLIs are installed and logged in, adds your first project from a folder picker, and offers to install the plugin into any CLI it finds.

Needs Node.js 20 or newer, and at least one of the four CLIs installed and logged in.