# 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.

Canonical page: https://capabilities.sh/status
Updated: 2026-11-06

> [!STATUS]
> **M1 is in progress.** As of 2026-11-06, 11 of the 20 M1 units are merged, 1 are in review and 8 have not started. Nothing is released yet.

## 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.

| Unit | What it builds | State |
| ---- | -------------- | ----- |
| LH-01 | Freeze the hub contracts | Merged (#28) |
| LH-16a | Add the eval harness, offline | Merged (#29) |
| LH-02 | Add port conformance suites and memory stores | Merged (#30) |
| LH-03 | Build the guest prelude | Merged (#32) |
| LH-05 | Add the code pipeline | In review (#37) |
| LH-06 | Add typegen | Merged (#35) |
| LH-07 | Add the index and search | Merged (#36) |
| LH-08 | Add the policy decision | Merged (#31) |
| LH-10 | Add the MCP source kind | Merged (#33) |
| LH-04 | Add the QuickJS sandbox driver | Merged (#38) |
| LH-11 | Add the local ports | Merged (#39) |
| LH-09 | Add runs with journal replay | Merged (#40) |
| LH-12 | Add the MCP surface | Not started |
| LH-17a | Run the early code-mode trial | Not started |
| LH-13 | Add the hub CLI commands | Not started |
| LH-14 | Add import and connect | Not started |
| LH-15 | Add the local approval page | Not started |
| LH-16b | Record the live eval baseline | Not started |
| LH-17 | Run code-mode evals round 1 | Not started |
| LH-18 | Add the local invariant suite | Not 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.