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.
Self-hosted control plane for AI agents: dispatch tasks, review runs, track spend, and operate OpenClaw, Claude Code, Codex, and other runtimes.
| Date | Stars |
|---|---|
| 2026-07-31 | 5884 |
| 2026-08-02 | 5884 |
| 2026-08-04 | 5918 |
| 2026-08-06 | 5918 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
35.0
growth rate 0.00%/day
<div align="center"> # Mission Control Self-hosted control plane for operating AI agents. Dispatch tasks, inspect runs, review failures, track spend, and coordinate agent runtimes from one local dashboard backed by SQLite. An open-source project by [Builderz Labs](https://builderz.dev), created and maintained by [nyk](https://nyk.dev). It works with OpenClaw, Claude Code, Codex, and other runtimes - it is not part of any one of them. [](https://github.com/builderz-labs/mission-control/actions/workflows/quality-gate.yml) [](https://github.com/builderz-labs/mission-control/releases) [](LICENSE) <img src="docs/mission-control-overview.png" alt="Mission Control overview dashboard with active sessions, live activity, fleet status per runtime, and the task pipeline" width="900"> </div> > [!WARNING] > Mission Control is alpha software. APIs, schemas, and configuration may change between > releases. Read the [security guidance](#security-boundary) before exposing it to a network. ## Start locally Node.js 22 or newer and pnpm are required for a source install. ```bash git clone https://github.com/builderz-labs/mission-control.git cd mission-control bash install.sh --local ``` Open `http://localhost:3000/setup`, create the first admin account, then copy the API key from Settings if an agent or script needs headless access. The manual path is useful when you already manage Node and pnpm: ```bash nvm use 22 pnpm install pnpm dev ``` Windows users can run `./install.ps1 -Mode local` in PowerShell. ### Start with Docker ```bash docker compose up ``` Or run the published multi-architecture image: ```bash docker pull ghcr.io/builderz-labs/mission-control:latest docker run --rm -p 3000:3000 ghcr.io/builderz-labs/mission-control:latest ``` Use the hardened Compose overlay for a network-accessible deployment: ```bash docker compose -f docker-compose.yml -f docker-compose.hardened.yml up -d ``` The [deployment guide](docs/deployment.md) covers persistent data, TLS termination, gateway connectivity, and standalone builds. ## What Mission Control governs The control plane sits above agent runtimes. It does not replace their reasoning or tool loops. It gives operators one place to see and govern the work around those loops. | Area | Shipped surface | |---|---| | Tasks | Inbox, assignment, execution, review, Aegis quality gate, and completion receipts | | Agents | Registration, presence, sessions, runtime adapters, configuration, and workspace sync | | Operations | Activity stream, schedules, alerts, webhooks, logs, token use, and cost views | | Knowledge | Memory browser, relationship graph, skills registry, and local skill synchronization | | Governance | Roles, API keys, security events, trust signals, approvals, audits, and evals | | Interfaces | Web UI, CLI, MCP server, OpenAPI-described REST API, WebSocket, and SSE | The runtime is self-hosted and workspace-aware. SQLite stores local control-plane state. Shared workspaces can use deployment-level runtime integrations. Strict workspaces block those integrations until the underlying resources carry workspace ownership. A gateway is optional for task, project, agent, scheduler, webhook, alert, and cost work; live session messaging needs a connected runtime gateway. ## Operator field notes Dashboards compress a sequence into current state. When a run needs review, record the identity, task, tool call, approval, result, and verification evidence before changing it. Keep unresolved items distinct from accepted risk.  Logs show what ran. A completion receipt or inspected artifact shows what finished. ## Pick the right fit Use Mission Control when m
Excerpt of 11,939 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:cc6ada8db24cefc8, topic:ai-agents, desc:ai agents
matched fp:cc6ada8db24cefc8, topic:developer-tools
matched fp:cc6ada8db24cefc8, topic:mcp
