Docs menu
Project Status
Status and roadmap
Where the hub stands. Milestone M1, the local hub, is in progress and nothing is released. The unit list is generated from the plan of record and the repository's history.
Milestones
| Milestone | What it delivers | State |
|---|---|---|
| M1 · Local hub | The engine and its approval page, run from a checkout: MCP sources, static credentials, the default code-mode profile, import, connect, review and the hub CLI |
In progress |
| M2 · Complete local | OpenAPI sources, OAuth, skills, large results as handles, the dashboard review inbox, named profiles, direct mode and run history | Planned |
| M3 · Hosted alpha | The same engine on Cloudflare at hub.capabilities.sh, reachable from cloud agents behind OAuth |
Planned |
| M4 · Paid launch | The hosted hub as a paid product, priced with data from the alpha | Planned |
M1 runs from a checkout build. An npx install waits for a later plan.
M1, unit by unit
M1 ships as twenty pull requests in dependency order. Each is verified by its own tests, live checks and a performance rule before it merges.
- Merged
- 11
- In review
- 1
- Not started
- 8
- LH-01Freeze the hub contractsMerged #28
- LH-16aAdd the eval harness, offlineMerged #29
- LH-02Add port conformance suites and memory storesMerged #30
- LH-03Build the guest preludeMerged #32
- LH-05Add the code pipelineIn review #37
- LH-06Add typegenMerged #35
- LH-07Add the index and searchMerged #36
- LH-08Add the policy decisionMerged #31
- LH-10Add the MCP source kindMerged #33
- LH-04Add the QuickJS sandbox driverMerged #38
- LH-11Add the local portsMerged #39
- LH-09Add runs with journal replayMerged #40
- LH-12Add the MCP surfaceNot started
- LH-17aRun the early code-mode trialNot started
- LH-13Add the hub CLI commandsNot started
- LH-14Add import and connectNot started
- LH-15Add the local approval pageNot started
- LH-16bRecord the live eval baselineNot started
- LH-17Run code-mode evals round 1Not started
- LH-18Add the local invariant suiteNot started
Journeys
The design spec defines six journeys that version 1 must make work end to end.
| # | Journey | Milestone |
|---|---|---|
| J1 | Import and connect: hub init --import finds your agents' MCP servers, and after hub connect each harness lists one capabilities server, in under two minutes |
M1 |
| J2 | A multi-step task, such as "summarize my open bugs and post the top 3 to #eng", runs as one execute over two sources with one approval for the post |
M1 |
| J3 | Add an API: hub add https://api.example.com/openapi.json asks for the key once, and the agent can call it |
M2 |
| J4 | A tool changes upstream: a refresh finds the new schema, and the next call asks again and says why | M1 |
| J5 | Go hosted: hub login and hub push, then add https://hub.capabilities.sh/mcp as a claude.ai connector |
M3 |
| J6 | Skills everywhere: a skill in the hub appears natively in every connected harness and is readable over MCP | M2 |
How this page is made
The unit list comes from the plan of record (docs/plans/2026-11-05-local-capability-hub.md) and the commit history of DeepAura/capabilities main, through scripts/sync-status.mjs, which reads a copy of both pinned at one commit. A unit shows as merged only when a commit on main names it. Units in review come from the open pull requests on the day that copy was taken.
Updated 2026-11-06