Commands

Every subcommand, grouped the way omni --help groups them: by what you are trying to do, not alphabetically.

omni <COMMAND> [FLAGS]
cmd | omni                # distill any command's output through a pipe

Set up

command	what it does
`init`	Install OMNI into your agent, hooks and MCP
`doctor`	Check the install is healthy, and fix what is not
`update`	Upgrade to the latest release
`reset`	Uninstall cleanly, keeping a backup of your config

See what it saved

command	what it does
`stats`	How many tokens were cut, and from which commands
`retrieve`	Print the content a marker archived, by its handle
`dashboard`	The same numbers in a browser, on 127.0.0.1
`diff`	The last command’s output, before against after
`session`	What this session has spent, and on what

Tune it

command	what it does
`exec`	Run one command through OMNI, to see what it would do
`query`	Search past distillations
`patterns`	Errors that keep coming back

Memory

command	what it does
`remember`	Save a fact for future sessions
`engram`	Digests of finished subtasks
`goal`	Pin a north-star goal so scoring favours it
`version`	Version and environment details

Hook entry points

Not for typing. These are what an agent host invokes, and they are documented in Hooks.

omni --pre-hook      omni --post-hook     omni --hook
omni --session-start omni --session-end   omni --pre-compact
omni --mcp

A note on how flags are parsed

A match on the first argument routes the subcommand and hands the module the raw env::args(), so every module parses its own flags and declares its own accepted set. cli::check_flags rejects anything outside that set, which is what stops omni stats --detial printing the default overview and exiting 0.

Per-command help is real and worth reading: omni <command> --help. Where this reference and the help disagree, this records what the source accepts.

Keyboard shortcuts