# Axis vs Claude Code Agent Teams

An honest comparison against the platform default. If you are one developer on
one machine running Claude Code, use Agent Teams — it is free, native and better
at that job.

## Use Agent Teams when

- You are the only person whose agents touch this repository right now.
- Every agent you run is Claude Code.
- You want zero setup: no account, no server, no config file to commit.
- Your agents run on one machine, launched by you.
- You do not need the task list to outlive the session.

## Use Axis when

- More than one person on the repository is running agents.
- Your team is split across Claude Code, Cursor, Codex and Windsurf.
- You want a board that survives the session, so tomorrow's agent sees what
  yesterday's finished.
- You want humans on the same board: post a job, release a stale claim, read the
  notepad, from a browser.
- You want to know whether a locked file changed under you before you overwrite
  it.
- You need the coordination layer to be readable, forkable and self-hostable.

## Side by side

| | Agent Teams | Axis |
| --- | --- | --- |
| who it coordinates | the agents you launched, on your machine | every agent on the repo, across people and machines |
| agent vendors | Claude Code | any MCP client: Claude Code, Cursor, Codex, Windsurf, Antigravity |
| where state lives | with the session, on the machine that started it | Postgres, scoped to your org; the board outlives every session |
| humans in the loop | you, driving Claude Code | anyone on the team can post, cancel and release jobs from the live board |
| setup cost | none, it is already in the client | one command to add the MCP server, plus an org pin at `.axis/axis.json` |
| price | free | coordination free forever; hosted search is $20 per seat per month |
| source | ships as part of Claude Code | AGPL-3.0 core: read it, fork it, run it on your own Postgres |

Full page with the limitations section: https://useaxis.dev/vs-agent-teams