Learn · Certification · Dev Tools
Technical: Dev Tools doors
Dev Tools has a command line, an MCP server, and a custom integration.
The ok command line includes init, sync, status, next, next-write, review, check-ok, governance-sync, verify-step, honesty-status, ledger, route, app, hosted-dashboard, adopt, mirror, upgrade-regime, land-check, land-closeout, pr-land, and handover-compact.
Agentception MCP tools validate a plan spec, validate a manifest, advance a phase, add or remove a GitHub label, comment on GitHub, claim a run, spawn an extra child, complete a run, cancel a run, and log a step or an error.
Agentception resources include active runs, pending runs, the dispatcher, and health.
The custom integration includes an optional Muse regime, a git mirror, opt-in editor hooks, a read-only hosted dashboard, GitHub issues and pull requests, a cloud or local model, Postgres, and Qdrant.
An operator starts that stack with Docker Compose.
The Dev Tools developer course teaches how these doors are built and customized.
Overseer Kit uses ok for planning and verification; Agentception uses MCP and its app to coordinate runs, issues, workers, and reviewers.
The operator chooses the model and starts the stack; Postgres holds application records and Qdrant supports retrieval, while GitHub carries the issues and pull requests.
| Door | What it is for |
|---|---|
| CLI | ok, for Overseer Kit. |
| MCP | Agentception tools over stdio and HTTP. |
| Custom integration | Optional Muse regime, git mirror, editor hooks, GitHub, a model, Postgres, and Qdrant. |