One repo context for every teammate
Generate config for 6 terminal CLIs + Cursor MCP bridge from the same ai/ source, so the team reviews one set of rules instead of seven private setups.
for engineering teams
Give every agent the same team rules.
0dai turns the team's agent workflow into repo-owned files: ai/for context, sessions for handoff, authority rules for review, and receipts for the merge trail.
team operating model
Scale the workflow without making agent memory private.
Roaming starts as files
Session handoff writes the goal, plan, touched files, and decisions to ai/sessions/active.json. Cross-machine roaming remains a planned sync boundary, not a hidden claim.
Governance before velocity
Team work is framed around authority YAML, RBAC, audit logs, and receipts so a faster swarm still leaves reviewable proof.
live vs planned
The team story separates what is live from what is planned.
Use Team when several developers need one governed agent workflow. Keep the near-term limits visible: file-backed roaming works locally today, while cross-machine sync and shared graph history are planned roadmap work.
Sync path
Team sync, shared cloud graph, and cross-machine graph history are marked planned in pricing copy.
Access path
RBAC, audit log, and admin controls are the current team governance story; SSO/SAML remains Enterprise.
Proof path
Governed-merge coverage is the value metric; PR-sized changes/day is a usage ceiling.
rollout proof
A team plan should answer procurement and code review.
The facts below are the same boundaries used by pricing and product facts: price, support surface, roaming scope, planned sync, and the value metric a team can audit after each merge.
Team priceTeam is $49/seat/mo; self-serve checkout supports up to 3 seats.
Agent surface6 terminal CLIs + Cursor MCP bridge; Team includes all 113 MCP tools by plan.
Roaming todayLocal session save and startup read are file-backed in ai/sessions/active.json.
Planned boundaryTeam sync and shared graph history are planned roadmap work, not claimed as live here.
Value metricGoverned-merge coverage
Start with 3 seats, then route larger rollouts through sales.
Use Team for governed shared workflows; route larger rollouts through contact sales.