Use it locally or in the cloud.
Start with the mb CLI — no server, no database, no API key. Create AI build contracts, validate changes into Matrix Commits, and sync to the cloud when you're ready.
mb is the git for AI builds.
MatrixHub is the GitHub for bundles.
Start locally in six commands.
Deterministic and offline. Everything lives in .mb/.
pip install agent-generator mb init "A GitHub repo intelligence agent" --quality standard mb next "Add repo ingestion" mb prompt --coder claude-code # paste into your AI coder mb check backend/app/... # approved → an immutable Matrix Commit mb timeline
What's on your disk — and how cloud compares.
├── project.json // version + cursors
├── blueprint.json // the controlled contract
├── batches/ // scoped change sets
├── prompts/ // per-coder prompts
├── validations/ // pass / repair reports
├── commits/ // immutable Matrix Commits
└── timeline // the full build history
Local mb | Cloud | |
|---|---|---|
| Drive with | terminal | browser |
| State in | .mb/ | Postgres + storage |
| Engine | local agent-generator | same engine, API |
| Setup | none | account + backend |
| Best for | devs, CI, offline | teams, sharing |
| Sync | optional | built in |
Work offline. Sync when ready.
Push your local Matrix Commits to the cloud; pull merged state back when your workspace changes.
mb login # self-issued session token mb sync # push commits ⇄ pull merged state
What works today?
Local mb CLI
Offline, deterministic, no infrastructure. The full loop — init, next, prompt, check, repair, timeline.
Cloud backend
Auth, the control-plane API, workflow tables, validation, repair, and run events — deployed and running.
Cloud web UI
The backend exists; the next step is wiring "My Builds" to the API instead of browser storage. Build with mb today.
AI coding needs a history.
Prompts disappear. Chats get messy. AI changes are hard to trust. Matrix Builder gives AI work a timeline you can replay, validate, and verify.