Scripting

All errors, warnings, and confirmation prompts print to stderr. For search, list, info, tune, scan, doctor, recommend, compare, evaluate, and bug-report, --json makes stdout a single structured document that is safe to pipe (for example, omm list --json | jq .). benchmark --json also writes a single JSON report to stdout; --output saves the same evidence as a file. Supported commands emit a structured error document when their command body fails before producing a result, and use exit status 130 with status: "cancelled" when interrupted. Argument-parser errors use a JSON error document when --json was requested, and stderr otherwise, with exit status 2. Successful data shapes remain unchanged.

For commands that document --yes/-y, pass it to skip their confirmation prompts, or use the command-specific flag (install --skip-unfit, install --upload/--no-upload). Benchmark upload consent remains governed by omm setting upload; for non-interactive benchmarks, start the selected local runtime before invoking the command.

These common flags are available on most top-level commands. Where supported, they may be accepted before or after the subcommand name (omm --json search foo and omm search foo --json are equivalent). Use omm COMMAND --help for the exact flags and placement of a specific command:

• --json — structured output, where supported (see above)
• --yes / -y — skip confirmation prompts
• --quiet / -q — suppress progress bars and background status/hint lines (e.g. download progress, "Verifying checksum...", scan's "Run: omm link" nudge); errors, warnings, and the result of what you asked for still print
• --no-color — disable ANSI colors on omm's own console output and its download progress bar; the NO_COLOR environment variable does the same

Unsupported --json combinations return a single unsupported_json error document and exit 2 before command actions or startup prompts run. JSON mode never opens the first-run setup/import dialogs, including on a terminal. omm --json --version returns a version document; explicit --help still shows normal help. The shared flag wrapper warns when --yes has no effect. Exit codes are consistent across commands: 0 success, 1 failure, and 2 usage error (bad flag or argument).

rm, ls, and up are short aliases for uninstall, list, and upgrade.

Set OMM_HOME to store everything (models, config, catalog history) under a different directory instead of ~/.omm — useful when $HOME's filesystem doesn't have room for GGUF models, e.g. OMM_HOME=/mnt/data/omm omm contribute --yes.

omm contribute keeps models and partial downloads already on your computer; it removes only the temporary models created by that session. Choose an optional time, model-data download, or new-model count limit, or combine them as above. The download limit is in GiB and includes retries; metadata and HTTP/TLS overhead are excluded. A time limit requests cancellation and then allows safe cleanup to finish. Without these flags, the loop continues until Esc or candidate exhaustion. The startup notice explains what is sent and whether the configured collector is public. The final summary separates successful measurements, accepted uploads, failed sends saved for retry, and the files kept or removed. The recommendation data contribution guide gives a one-model starting point, cross-computer instructions, and the current quality-data limits.

omm contribute performs a 10 GiB startup free-space preflight. Before each download it separately budgets the central GGUF, a worst-case full runner copy, any required Windows cross-volume copies, and safety headroom. Each model evaluation prints a heartbeat every 30 seconds and is terminated after an absolute 10-minute deadline instead of hanging an unattended session indefinitely.

Localfit does not assume all installed memory belongs to the model. A live scan subtracts memory currently used by other applications, keeps at least 2 GB (or 10% of RAM) for the OS and newly opened apps, and applies total-memory caps. Recommendation fit and omm tune use this safe budget, so rerunning a command adapts after memory-heavy applications are opened or closed.

omm benchmark runs a versioned eight-item bilingual arithmetic smoke pack against models already installed in the selected Ollama or LM Studio runtime. It stores parsed answers, correctness, pinned model metadata, and fixed-length timings under OMM_HOME/evaluations/ (default ~/.omm/evaluations/); it stores no generated text. Opt-in telemetry sends a locally computed CPU chip score (and GPU chip score, when a GPU is present) plus architecture and core counts — never the raw CPU/GPU model name — so speed predictions can distinguish otherwise identical Linux x86_64 machines. Results are uploaded only after explicit opt-in. The pack is intentionally small and is not a leaderboard.

On Windows, Ollama is detected by its HTTP API first, so a freshly installed tray app works even before the current terminal receives the new PATH. When the daemon is stopped, omm also checks Ollama's documented %LOCALAPPDATA%\Programs\Ollama location. It only stops daemon processes it started itself. Before deleting a contribution model, omm requests an Ollama unload, waits for /api/ps to confirm handle release, and uses bounded retries for Windows file locks. Real-time antivirus can still delay a first load; the benchmark uses repeated samples and reports their median. Do not disable your antivirus for omm.