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 |
Today
+1 stars today
This week
— stars this week
This month
— stars this month
Momentum
39.0
growth rate 0.00%/day
[English](README.md) | [中文](README.zh-CN.md) # AI Team OS <!-- Logo placeholder --> <!--  --> ### Your AI coding tool stops when you stop prompting. Ours doesn't. > ⚡ **v1.11.1** — A governance patch: the ledger stopped misreporting itself. The whole database moved onto one clock (UTC, with a single conversion point at the storage boundary — the silent 8-hour cross-domain skew is now a loud `TypeError`); token usage gained a billing metric for the first time and no number is ever shown without its coverage denominator (sub-agent attribution 0.7% → 78.5% after backfill); task failures are booked by the state machine instead of by an agent's self-report; and every model-facing prompt was audited against one rule — state only what the reader cannot derive. New `/usage` diagnostic page, one new MCP tool (112 → 113), machine-checked invariants 9 → 14. [](https://python.org) [](LICENSE) [](https://fastapi.tiangolo.com) [](https://react.dev) [](https://modelcontextprotocol.io) [](https://github.com/CronusL-1141/AI-company) **113** MCP tools · **207** REST endpoints · **23** dashboard pages · **2,307** tests · **25** agent templates · **42** ecosystem research tools · **14** machine-checked invariants --- AI Team OS turns Claude Code into a **self-driving AI company**. You're the Chairman. AI is the CEO. Set the vision — the system executes, learns, and evolves autonomously. --- ## The Problem With Every Other AI Tool Every AI coding assistant works the same way: you prompt, it responds, it stops. The moment you step away, work stops. You come back to a blank prompt. AI Team OS works differently. You walk away at night. The next morning you open your laptop and find: - The CEO checked the task wall, picked up the next highest-priority item, and shipped it - When it hit a blocker that needed your approval, it parked that thread and switched to a parallel workstream - R&D agents scanned three competitor frameworks and found a technique worth adopting - A brainstorming meeting was organized, 5 agents debated 4 proposals, and the best one was put on the task wall You didn't prompt any of that. The system just ran. --- ## How It Works **You're the Chairman. The AI Leader is the CEO.** The CEO doesn't wait for instructions. It checks the task wall, picks the highest-priority item, assigns the right specialist Agent, and drives execution. When blocked, it switches workstreams. When all planned work is done, R&D agents activate — scanning for new technologies, organizing brainstorming meetings, and feeding improvements back into the system. Every interaction makes the system understand you better. **Memory System v2** distills your preferences and corrections into a team direction layer that every dispatched Agent inherits at birth — you never say the same thing twice, and no next Agent repeats a pit an earlier one already fell into. --- ## Core Capabilities ### 1. Cross-Session Orchestration (new in v1.10.0) A single CC session can now observe and drive its sibling sessions for one operational turn, instead of only being able to spawn brand-new ones: - **Wake system v2**: the `/api/wake/actionable` single-source predicate feeds both the event watcher and the turn-end guard; SessionStart moves from a fixed 30-minute cron to dynamic `/loop` intervals; a Stop-hook turn-end guard always lets `decision:block` and user-stop keywords pass through; a session-scoped event watcher carries a 1-hour hard timeout. No resident daemons. - **Fleet downlink primitive**: headless `claude -p --resu
Excerpt of 53,832 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:5331736472e21410, topic:ai-agents, topic:autonomous-agents, topic:agent-framework
matched fp:5331736472e21410, topic:mcp, topic:mcp-server