Repository navigation
Home
A team of AI agents across labs, for your software project.
No agent is best at everything. Where a lab offers its own multi-agent tool, it builds a team of that lab's agents; TeamCLI is for the team that spans labs — Claude, GPT, Grok, Gemini, DeepSeek and more, from different companies, working as one team under one set of rules. That cross-lab team is why TeamCLI exists: a review by a different lab is independent to the degree the labs genuinely differ, when one lab's limit or outage hits the rest can carry the work, and each role goes to the agent that fits it.
TeamCLI runs on any git repository — local, or hosted on any forge — and it is honest about what it protects: it guards against a mistaken agent, not a hostile one, and every commitment says what is true in the released version today.
- Tier 0 — Charter (accepted 2026-10-11). What we believe, what a team is and how it lives, and how we decide.
- Tier 1 — Kernel (accepted core; three sections still draft). The one enforced layer of authority, capabilities and trust.
- Tier 2 — Runtime (draft). How a team is configured, run and observed.
- Tier 3 — the modules (drafts): 002 Communication, 003 Memory, 004 Measurement, 005 Quality, 006 Consensus, 008 Planning, 009 Roles and skills, 010 Workflow.
- Governance (drafts): Board, Review terms, Norms and practices.
The full list, with each page's status, is in the RFCs index.
- The Charter states the beliefs and the decision rules.
- The Kernel states the enforced capabilities and gates.
- The Runtime and the modules carry the design of the work.
- The specifications are the living formats, fields, codes and schemas that implement these commitments; each RFC links to the parts it relies on.
The earlier public RFCs 000–009, and the earlier Kernel and Architecture pages, remain readable under History, unchanged apart from their links and one outdated term. The earlier RFC index is the way in.