Install

Get the binary

macOS and Linux, via Homebrew:

brew install fajarhide/tap/omni

macOS, Linux, WSL:

curl -fsSL omni.weekndlabs.com/install | bash

Windows, PowerShell:

irm omni.weekndlabs.com/install.ps1 | iex

From source, which needs the toolchain pinned in rust-toolchain.toml:

git clone https://github.com/fajarhide/omni
cd omni
cargo build --release

From inside Claude Code, if you would rather have the agent do the rest:

/plugin marketplace add fajarhide/omni
/plugin install omni@omni

On any agent that reads skills, the same skill installs through the skills directory CLI, and is listed at skills.sh/fajarhide/skills/omni:

npx skills add fajarhide/skills --skill omni

Either way that installs a skill, not the binary. The skill carries the install commands below, the verification step, and how to read the markers, so the agent stops guessing at any of the three. Everything on this page still applies; the plugin only means someone else types it.

Wire it into your agent

omni init            # the host you are running in, or a menu if you have a terminal
omni init --claude   # or --cursor, --codex, --gemini, and 11 more
omni init --all      # every host, and a .vscode/mcp.json in the current directory

omni init writes hooks and registers the MCP server. It is idempotent, so running it again after an upgrade is the right move rather than a risk.

With no terminal to prompt on, which is how an agent runs it, omni init configures the host it is running inside instead of failing on the absent menu. It says which host it picked. If it cannot name the host, a plain shell for instance, it stops and asks for a flag rather than installing into somewhere nobody asked for.

Every supported flag is in init. Which hosts get what is in Supported agents, and that page matters more than it sounds: a host that cannot rewrite its own shell tool’s output will not show the agent distilled bytes however well the pipeline works.

Verify

omni doctor

This is not optional ceremony. It checks the binary is on PATH, the database opens, the hooks are actually installed where the host reads them, and the MCP server is registered. omni doctor --fix repairs what it can.

Codex CLI needs one extra step. It runs only hooks it has been told to trust and skips the rest silently. After omni init --codex, start codex once and approve them under “Hooks need review”. omni doctor will keep failing until you do.

Confirm it is really running

omni doctor says the wiring is correct. This says the wiring is being used:

cat some-long-file.txt     # through your agent, not this shell
omni diff                  # raw against distilled, for the last command
omni stats

If omni stats shows rows and omni diff shows a difference, the hook is live.

A trap worth knowing now rather than later: the numbers in omni stats are split by agent_id, and a row recorded under terminal is TTY output no model ever read. When you are judging whether OMNI is earning its place, look at the rows for your actual host.

Upgrade

omni update      # Homebrew installs
brew upgrade omni

Re-run omni init afterwards if a release changes the hook contract. The changelog says when that happens.

Remove it

omni init --uninstall   # hooks and MCP registration for one host
omni reset --all        # every integration, and offers to wipe omni.db

omni reset without flags gives an interactive menu. Neither command touches your shell configuration, because OMNI never wrote any.