English | 中文

AI Team OS

Shared context, accountable work, native agents.

AI Team OS is a shared operating layer for Claude Code and Codex. Keep tasks, project memory, reports and team messages in one place, and follow work across sessions in one Dashboard. Each host keeps its native agent tools; the OS provides the durable record that makes their work understandable and reusable.

🤝 Codex is supported. Use Codex or Claude Code on its own, or connect both to the same OS task wall, project memory, reports, channels and Dashboard. Codex uses its own MCP and hook configuration; native agent tools, host settings and hook trust remain separate. See the installation and capability sections below for the per-host setup and boundaries.

⚡ v1.15.2 - A task wall you can manage, and receipts for external Codex runs. Tasks get real parent and child links, dependencies that unlock downstream work when they complete, explicit waits, clearable fields, revision checks and atomic batch creation. The opt-in aiteam codex-exec keeps minimum usage receipts for codex exec runs, including --ephemeral runs that leave no rollout. aiteam attribution repair lets every install correct usage rows stored before the upgrade, and the Codex usage backfill now runs on freshly installed databases. Some task-update semantics changed (an empty string now clears a field); after updating, restart the API and every open Claude Code and Codex session; see the changelog.

Full version history: CHANGELOG.md

118 MCP tools · 241 REST endpoints · 24 dashboard pages · 25 agent templates · 42 ecosystem research tools · 27 machine-checked invariants

---

A session can end without taking the team's context with it. Tasks, memos, decisions and reports remain available to the next authorized session, whether it runs in Claude Code or Codex.

---

What Carries Across Sessions

Parallel agents are useful only when you can tell who owns the work, what actually happened and where to resume. AI Team OS keeps those answers outside any single chat:

• Tasks and handoffs: ownership, progress memos, blockers and completion records stay on the project task wall.
• Project memory and reports: retrieve earlier decisions and evidence instead of rebuilding context from scratch.
• Team communication: send and read project-scoped messages across hosts, with explicit reader identities and acknowledgements.
• Operational visibility: inspect Leaders, members, tool activity and project-level totals in one Dashboard.

The OS records and exposes the work. Your chosen host runs the agents, and you decide what they are authorized to do.

---

How It Works

You set the scope. Each root session has its own Leader. A Claude Leader and a Codex Leader can contribute to the same project without pretending to be the same process or sharing host configuration.