Both plans run every harness, the console, the CLI and the API. Team adds the seats, the projects and the retention a team needs.
One person, their agents, up to three repos.
A team sharing one memory across repos and harnesses.
The difference is how many people and repos, and how long raw turns stay. Everything else is on both plans.
| Free | Team | |
|---|---|---|
| Size | ||
| Seats | 1 | As many as you subscribe to |
| Projects | 3 | 100 |
| Raw turn retention | 7 days | 30 days |
| Items | Unlimited, kept until retracted | Unlimited, kept until retracted |
| Memory | ||
| Recall at session start | Yes | Yes |
| Items: facts, decisions, gotchas, conventions | Yes | Yes |
| Shared items across the team | One seat | Yes |
| Live awareness: who is in which files | One seat | Yes |
| Fork memory to another branch or repo | Yes | Yes |
| Retract an item | Yes | Yes |
| Harnesses and tools | ||
| Claude Code, Codex, Cursor, Antigravity, pi, opencode, OpenClaw | All | All |
| Console, CLI, API, SDK | Yes | Yes |
| Client-side secret redaction before upload | Yes | Yes |
| Sign in with Google, Microsoft or an email code | Yes | Yes |
| Organization | ||
| Roles | Owner | Owner, admin, member |
| Invite by email | No seats to fill | Yes |
| See and revoke every agent session | Yes | Yes |
| Export the organization as JSON | Yes | Yes |
| Billing | None | Card through Stripe, monthly |
Nothing you already have stops working when you reach a limit. The next thing that would grow past it is refused.
One person who can sign in to the organization, plus any invite they have not yet accepted. Agents, sessions and machines are not seats. One person running four harnesses uses one seat.
One repository, identified by its origin remote. Branches, forks of memory inside it and every teammate's checkout of it are the same project.
Raw turns are the recorded prompts and replies of a session. They stay private to the person who wrote them and expire after the plan's retention window. Items are the short facts, decisions, gotchas and conventions an agent writes at checkpoints. They are the shared layer, they do not expire, and anyone on the team can retract one.
Owners open the billing portal from the Org page of the console and change the quantity. The change applies at once and Stripe prorates the difference on the next invoice.
Team runs until the end of the paid period, then the organization returns to Free. Nothing is deleted. Members and projects stay, and the Free limits apply to the next invite and the next new project. Raw turns older than seven days expire.
No. An item stays until someone on the team retracts it or the organization is deleted. Retention windows apply to raw turns only.
No. All seven harnesses, the console, the CLI, the API and every sign-in method are on both plans.
Only with 30 days of notice to organization owners by email, and only from your next renewal. The terms say the same.