An open-source multi-agent coding CLI that allows users to switch AI models mid-session and complete goals only when specified tests pass.
Also known as dmae97/omk, open-multi-agent-kit
- Stars
- 153
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 15, 2026
- License
- MIT
What is OMK MCP?
OMK is an open-source multi-agent coding CLI that allows users to switch AI models mid-session and complete goals only when specified tests pass.
Summary generated from the project's README
About OMK MCP server
Developers looking for a terminal-based coding assistant can use this multi-agent CLI to manage complex programming tasks. It functions as a standalone tool that runs locally within your git repository, allowing you to switch between different AI providers, API keys, or local models mid-session without losing your conversation history.
Unlike standard agents that simply report when a task is finished, this tool requires an explicit verification step. By using the /goal verify command, you define a specific test or shell command that must exit with a zero status before the agent considers its work complete. This ensures that code changes actually meet your requirements. The environment is sandboxed by default using tools like sandbox-exec or bwrap to run bash commands without network access, providing a secure way to execute agent-generated code.
What you can do with it
- 1Enforce passing testsInstruct the agent to fix a bug and only stop once a specific test command passes.
- 2Switch AI modelsChange the underlying model during an active coding session to better suit the current task.
- 3Resume interrupted workReturn to a previous coding session later by using the resume command.
- 4Secure code executionRun agent commands in a restricted environment to prevent unauthorized network access.
Written from the project's README. Every use case is checked against a quote from it.
How to install OMK MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall OMK MCP in Claude Code
$ claude mcp add omk -- npx -y open-multi-agent-kitInstall OMK MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"omk": {
"command": "npx",
"args": [
"-y",
"open-multi-agent-kit"
]
}
}
}Install OMK MCP in VS Code
.vscode/mcp.json
{
"servers": {
"omk": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"open-multi-agent-kit"
]
}
}
}Install OMK MCP in VS Code CLI
$ code --add-mcp '{"name":"omk","type":"stdio","command":"npx","args":["-y","open-multi-agent-kit"]}'Install OMK MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"omk": {
"command": "npx",
"args": [
"-y",
"open-multi-agent-kit"
]
}
}
}Install OMK MCP in Codex
$ codex mcp add omk -- npx -y open-multi-agent-kitInstall OMK MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.omk] command = "npx" args = ["-y", "open-multi-agent-kit"]
Install OMK MCP in Gemini CLI
$ gemini mcp add -s user omk npx -- -y open-multi-agent-kitInstall OMK MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"omk": {
"command": "npx",
"args": [
"-y",
"open-multi-agent-kit"
]
}
}
}Configuration
OMK_CONTEXT_GOVERNOR
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHub| CONTROL | CHOICE | EVIDENCE |
|---|---|---|
| Keep the work in your terminal and repository. | Switch providers and models in one session. | Define a check before a goal can complete. |
OMK is a lightweight, MIT-licensed AI coding agent for your terminal, written in TypeScript. Switch models in one session, add subagents when you need them, and mark a goal done only when your own check passes. It is a standalone CLI, so it can serve as an open-source alternative to a single-provider agent such as Claude Code.
60-second start
You need Node.js 22.19 or newer and a git repository that has a test command.
npm install -g open-multi-agent-kit --ignore-scripts
cd your-project
omk
On the first run OMK opens /login (subscription, API key, or local model).
Then, inside OMK, give it a goal and name the check:
/goal Fix the failing test without changing its assertions.
/goal verify npm test
OMK asks you to approve the command, runs it, and runs it again after each
settled turn. The goal completes only when it exits 0. Swap npm test for your
project's own check.
No global install? Run npx --ignore-scripts open-multi-agent-kit. The
standalone binary and the setup details are in Quick start.
If omk helps you, a ⭐ on GitHub helps other people find it.
Why OMK
An AI saying “done” is not an acceptance check. With /goal verify, you choose
the command that checks your goal. OMK runs it after each settled turn and
completes the goal only when it passes on the current workspace. A later edit
makes that evidence stale. The result is only as strong as the check you choose.
/goal Fix the failing test without changing its assertions.
/goal verify node --test check.test.mjs
Use a test that exists in your project, or follow the small, reproducible goal demo. This is an explicit workflow; ordinary prompts do not enable the gate.
Choose a model, work on your repository, then switch models with /model when
another one suits the next step. The conversation stays in the same session.
You can also stop and return later with /resume or omk -c.
OMK is a standalone CLI, not a plugin for Claude Code or OpenCode. It supports subscription providers, API keys, and local models. Start with one agent that reads files, edits code, and runs commands. Add subagents or explicit verification workflows when you need them; neither is required for your first task.
At a glance
- Done means a passing check.
/goal verify <command>completes a goal only when your check passes on the current workspace. - One session, many models. Switch with
/modelmid-conversation; resume later with/resumeoromk -c. - Sandboxed by default. Built-in bash runs under
sandbox-execorbwrap, without network, and fails closed. - Opt-in power. Subagents, MCP servers, skills and extensions load only when you configure them.
- Honest evidence. Claims below link to the docs that back them, and the limits are stated next to them.
flowchart TD
P["Prompt or goal"] --> A["Agent loop"]
A --> S["Settled turn"]
S --> R["Response"]
S -->|"goal verification configured"| V["Run acceptance check"]
V -->|"pass on current workspace"| D["Goal complete"]
V -->|"fail"| A
The loop uses your selected model and available tools. Subagents, MCP, skills, and extensions depend on your configuration.
Quick start
Install from npm (Node.js 22.19 or newer), then start in your repository:
npm install -g open-multi-agent-kit --ignore-scripts
cd your-project
omk
Or run npx --ignore-scripts open-multi-agent-kit without a global install.
Or install the standalone binary, which needs no Node.js (macOS, Linux):
curl -fsSL https://github.com/dmae97/omk/releases/latest/download/install.sh | sh
The script checks the download against the release's SHA256SUMS and installs
to ~/.omk/bin; add that folder to your PATH as it tells you. Windows builds
are attached to each release.
- On a first run OMK opens
/loginfor you: sign in with a subscription or an API key. An existing Claude Code or Codex CLI login can be reused withomk provider adopt. - Run
/modelto choose another available model at any time. - Try a read-only first task:
Summarize this repository and identify the commands used to check it.
Read the project configuration to support your answer. Do not edit files.
After the reply, use /model to choose another configured model and ask it to
review the answer. You stay in the same session. This is manual model switching,
not parallel agents or an independent correctness check.
Ready to see a test-backed goal? Try the goal demo, then share your result or a reproducible failure in a GitHub issue. If this workflow is useful, star OMK to help other developers find it.
For a bug fix, name the failing behavior and ask for a regression test, the smallest fix, and the check commands with their exit codes. Review the diff and those results yourself; a request to run tests does not enable a verification gate.
Built-in local bash requires sandbox-exec on macOS or bwrap plus
unprivileged user namespaces on Linux (sudo apt install bubblewrap on Debian
and Ubuntu). It blocks network access and fails closed if the backend is missing.
omk doctor checks the runtime, credentials, the model a first session would
pick, and the sandbox, and prints the fix for this machine. See
Bash sandbox setup, the
safety boundary and the
full quickstart.
What runs by default
A fresh install starts one agent/tool loop after provider setup. It does not turn each prompt into a multi-agent workflow or automatically certify its answer.
| Capability | Fresh-install behavior | Where to start |
|---|---|---|
| File editing, shell commands, saved sessions | Built in; tools run when called by the agent | Usage, sessions |
| Tool-call scheduling | dag-v2 schedules resource conflicts within the agent loop; it does not launch a team |
Runtime algorithms |
| Subagents | Optional extension; load it and supply agent definitions | Subagent setup and examples |
| MCP servers, extra skills and extensions | Require configured servers or installed resources | MCP, skills, extensions |
| Durable goals | Built in; /goal <objective> continues after each settled turn, up to 8 rounds. With /goal verify <command> the goal completes only when that check passes on the current workspace |
Acceptance checks |
| Protocol verification and advisory judging | Explicit API/workflow opt-in; not a gate on ordinary prompts | Run protocol |
Verified runs (omk run) |
Opt-in CLI and SDK on Linux with bwrap; runs an approved command in an isolated copy, checks the result, and supports resume, cancel and cleanup |
Verified run |
| Context budgeting | Off by default | Settings |
| AdaptOrch integration | Optional and separate; no service calls by default | OMK + AdaptOrch |
The internal lane launcher and automatic command-sharding primitives are not connected to the default CLI path. Installing their packages is not the same as enabling an orchestration workflow.
Context, cache and memory
OMK manages several distinct resources. A prompt-cache boundary, a local cache, and the process's RAM are not the same thing; provider cache hits and costs depend on the provider and the request.
| Layer | What OMK does | Default and scope |
|---|---|---|
| Prompt prefix | Preserves the cache boundary when an extension changes only the dynamic tail and the prefix matches byte for byte. | On by default; this does not guarantee a provider cache hit. OMK_PREFIX_BOUNDARY |
| Context Budget V2 | Reserves response and safety space, keeps required items, and selects representations of optional context that fit. | Off by default; enable globally or for a process. Context selection |
| Local context cache | Reuses eligible representation and negative-result entries; cached plans stay in session memory. | Only when Context Budget V2 is enabled. Representations persist per workspace by default; a memory-only option is available. Settings |
| Session history | Compaction can summarize earlier context; saved sessions support resume. | Compaction and its settings are separate from persistent knowledge and provider-side caches. Sessions |
| Host resources | The resource governor can observe host capacity and admission decisions. | observe is the default; adaptive throttling requires configuration. Resource governor |
For one process, opt into context budgeting and keep its cache in session memory:
OMK_CONTEXT_GOVERNOR=1 OMK_CONTEXT_GOVERNOR_CACHE=memory omk
Memory-only changes where entries are kept; it is not a guarantee of lower RAM use. Cache effectiveness, memory use, latency and cost depend on the workload. Measure them before claiming an improvement; turn metrics show what can be recorded.
Evidence and limits
One dated comparison is available below: OMK and mini-SWE-agent on Terminal-Bench 2.1 with the same base model. The observed success-rate difference is not statistically significant, and the time budgets differed. It does not establish overall harness superiority, multi-agent gains, or how much verification reduces false completion.
OMK targets state-of-the-art quality as a CLI coding-agent harness. SOTA is not verified.
The evidence you can inspect today covers specific failure modes:
| Behavior covered | Regression evidence | Scope |
|---|---|---|
Missing test observations produce inconclusive; a required failing test produces fail |
Protocol tests | Explicit protocol evaluation, without a waiver |
| Changed artifacts, wrong command bindings, or missing ledger evidence block acceptance | Evidence binding tests | Strict evidence gate and selected workspace scope |
| A relevant workspace mutation after verification makes the receipt stale | Freshness tests | Configured receipt and mutation tracking |
| A durable goal with an approved acceptance check completes only on a passing receipt, and an edit after the check makes that receipt stale | Goal acceptance tests, live loop tests | Approval held by the running OMK process; git work tree; static command lines |
| An effect that may still be live keeps its resource claims through expiry, cancellation and authority restart, until a supervisor confirms termination | Coordination broker tests | In-process broker with canonical claim keys; no OS fencing |
| A publication is refused unless its read versions, parent revision and receipt binding all still match | Publication tests | Single accepted snapshot pointer; no multi-file filesystem atomicity |
| Cancellation after dispatch is never reported as cancelled-before-dispatch; the outcome stays unknown until settled | Operation lifecycle tests | Pure state machine; does not itself stop a remote effect |
| Zero trials is reported as absent evidence rather than zero risk, and a point estimate is not an error rate | Risk bound tests | Binomial model under a fixed policy and adequately independent samples |
These tests exercise the gates, not the rate at which they catch real bugs.
An ordinary prompt finishes when its tool loop and queued work settle;
prompt_settled is not a correctness verdict.
A useful comparison must hold the model, provider configuration, tasks, budget,
and tool permissions constant, and label default versus opt-in workflows.
Report task success, cost, latency, and false completion (reported complete but
failing the declared checks), with its denominator and per-task outcomes.
The measurement protocol
defines the reproducibility and privacy requirements. omk stats shows local
turn costs and tool failures; it does not score task correctness.
If you evaluate OMK, share a sanitized report and reproduction steps in a GitHub issue. Include failed and interrupted runs, not just successful examples.
OMK MCP questions
How do I add OMK MCP to Claude Code?
Run claude mcp add omk -- npx -y open-multi-agent-kit in your terminal. Add --scope user to make it available in every project.
How do I add OMK MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I ensure a goal is actually completed?
You can use the /goal verify <command> instruction to define a specific check that OMK must pass before the goal is marked as done.
Can I change the AI model during a coding session?
Yes, you can switch providers and models within a single session using the /model command.
Is the execution environment secure?
Yes, built-in bash commands run in a sandbox using sandbox-exec or bwrap, which lacks network access and fails closed.