How do I install OMK?

With Node.js 22.19 or newer, run npm install -g open-multi-agent-kit --ignore-scripts, then omk in your project. Without Node.js, use the standalone installer on macOS or Linux: curl -fsSL https://github.com/dmae97/omk/releases/latest/download/install.sh | sh. See Quick start.

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.

1. On a first run OMK opens /login for you: sign in with a subscription or an API key. An existing Claude Code or Codex CLI login can be reused with omk provider adopt. 2. Run /model to choose another available model at any time. 3. 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.

Published packages

npm install omk-agent-core
npm install omk-ai
npm install omk-protocol
omk install npm:omk-book-to-skill@0.98.3
npm install omk-tui

</details>

How is this different from OpenCode with plugins?

OMK is a separate runtime with its own CLI, sessions, tool scheduler, and SDK. One reason to choose it is to build your own acceptance workflow: define required test observations in the run protocol, then have your automation reject fail or inconclusive results. Receipt integrity and freshness still need their own configured checks.

For adding a tool or prompt to an existing OpenCode setup, a plugin may be the smaller change. OMK's protocol is opt-in, not proof of better performance.

FAQ