Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Multi-agent team operating system for Claude Code. 108 MCP tools, 40+ agent templates, 10 lifecycle hooks, 7 pipeline workflows. Persistent teams, structured meetings, task wall, real-time React dashboard. No LangChain/AutoGen — pure CC native integration.
| Date | Stars |
|---|---|
| 2026-07-31 | 327 |
| 2026-08-01 | 331 |
| 2026-08-02 | 334 |
| 2026-08-03 | 333 |
| 2026-08-04 | 334 |
| 2026-08-05 | 337 |
| 2026-08-06 | 338 |
| 2026-08-08 | 339 |
| 2026-08-09 | 340 |
| 2026-08-10 | 340 |
| 2026-08-11 | 341 |
| 2026-08-12 | 341 |
| 2026-08-14 | 341 |
| 2026-08-15 | 342 |
| 2026-08-17 | 343 |
| 2026-08-18 | 344 |
| 2026-08-20 | 344 |
| 2026-08-21 | 345 |
| 2026-08-23 | 346 |
| 2026-08-25 | 346 |
| 2026-08-26 | 348 |
| 2026-08-28 | 349 |
| 2026-08-29 | 351 |
| 2026-08-31 | 352 |
| 2026-09-01 | 353 |
| 2026-09-02 | 354 |
| 2026-09-03 | 356 |
| 2026-09-06 | 357 |
| 2026-09-07 | 358 |
| 2026-09-09 | 357 |
| 2026-09-14 | 359 |
| 2026-09-16 | 360 |
| 2026-09-17 | 361 |
| 2026-09-19 | 361 |
| 2026-09-20 | 361 |
Today
— stars today
This week
+4 stars this week
This month
+16 stars this month
Momentum
39.0
growth rate 1.12%/day
[English](README.md) | [中文](README.zh-CN.md) # AI Team OS <!-- Logo placeholder --> <!--  --> ### 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. <!-- Keep the Codex compatibility note above across releases. For each release, replace the current-release announcement with that version's verified summary. Keep historical details in CHANGELOG.md. --> > ⚡ **v1.12.4 — Shared-host observations and runtime reliability.** This batch improves Claude/Codex Leader attribution, native member names and parent teams, and current-work visibility; fixes project-scoped events and Analytics, cross-team totals and tool-completion pairing; and adds legacy session-team collision repair and runtime diagnostics. See the changelog for validation results, upgrade requirements and remaining limitations. > > Full version history: [CHANGELOG.md](CHANGELOG.md) [](https://python.org) [](LICENSE) [](https://fastapi.tiangolo.com) [](https://react.dev) [](https://modelcontextprotocol.io) [](https://github.com/CronusL-1141/AI-company) **116** MCP tools · **211** REST endpoints · **23** dashboard pages · **25** agent templates · **42** ecosystem research tools · **21** 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. 1. Resolve the project and read its task wall, relevant memos and memory. 2. Let the session's Leader coordinate authorized work using its host's native agent tools. Members belong to their parent team; Codex's native nicknames stay distinct from roles and task names. 3. Record progress, decisions and reports through the shared MCP tools. Other sessions can pick them up through the same project records and channels. 4. Inspect the Dashboard to compare r
Excerpt of 61,810 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:33af5a75991013ef, topic:ai-agents, topic:autonomous-agents, topic:agent-framework
matched fp:33af5a75991013ef, topic:mcp, topic:mcp-server