omni exec

Runs one command through the full pipeline and prints the result, with a footer showing what it cost.

omni exec cargo test

cargo test: 411 passed, 1 failed
  FAILED ledger::tests::renders_identical_bytes_for_identical_state
[OMNI Active] ⏺ 93.7% reduction (2.3 KB → 147 B) 3ms

This is the harness every bug report in this project is asked to use, because it takes the host out of the picture. If a corruption survives omni exec, it is OMNI.

The argument form is exact

omni exec cargo test          # correct
omni exec -- cargo test       # fails: No such file or directory
omni exec 'cargo test'        # works, single-string form
omni exec sh -c 'a; b'        # works, split-argv form

The -- form is the one people reach for and the one that does not work.

Flags

Both are what the pre-hook uses when it rewrites a command into omni exec.

--session is worth knowing when you are investigating ledger behaviour: it is the only way to drive two distinct sessions by hand and see the difference between an already shown fold and a not shown here fold.

Isolate the database while probing

Output is not deterministic against a warm database, because session history feeds the scorer. Give each probe its own:

OMNI_DB_PATH=/tmp/probe.db omni exec <command>

A warm shared database also serialises writes, which is the usual reason omni exec appears to hang.

Related

omni diff shows the same before and after for the last command the hook processed, which is what you want when the interesting command already ran.