omm

omm setting

View or change telemetry, what anonymous data may leave this machine, memory protection, the update channel, the color theme, calibration, and signed-catalog trust — interactively, or one subcommand at a time.

01 / 06

Overview

Reach for setting any time you want to see or change how omm behaves outside of a single command. Bare omm setting opens an interactive menu covering the same ground as every subcommand below; each subcommand also works directly, prints a small table of its current value either way, and every write here stays local — nothing is uploaded just by changing a setting. Everything omm may ever send is now grouped under one subcommand, omm setting upload, with a separate policy per channel: benchmark results, anonymous usage stats, and crash reports. Usage stats and crash reports are off until you turn them on.

02 / 06

Options

Every flag this command accepts, and what it defaults to when you leave it out.

  • setting telemetry --endpoint URL—Default: not configured

    Configure where benchmark telemetry is sent, or clear it with --endpoint none.

  • setting upload—Default: show all three policies

    Show all three outbound-data policies — benchmark, usage, crash — in one table.

  • setting upload benchmark --enable|--disable|--ask—Default: ask

    Configure whether benchmark results upload without asking, never, or ask each time.

  • setting upload usage --enable|--disable|--reset-id—Default: off

    Anonymous daily usage stats: omm version, install method, OS, CPU/GPU class, RAM and VRAM size ranges, and which commands ran. Never model names, search terms, file paths, IP, or hostname. With no flag it prints the exact payload that would be sent next; --reset-id generates a new random install id.

  • setting upload crash --enable|--disable|--ask—Default: off

    Configure the separate, opt-in policy for scrubbed crash reports, sent on their own write-only channel.

  • setting memory-guard --policy ask|block|observe --poll-seconds N --low-memory-seconds N—Default: show current values

    Configure Memory Guard's policy, polling interval (0.1–60 seconds), and how long low memory must persist before cancellation (0–300 seconds).

  • setting version --stable|--beta—Default: stable

    Show or switch which branch omm update pulls from.

  • setting theme --set NAME—Default: dark

    Show or change omm's output color theme.

  • setting calibrate [name]—Default: smallest Ollama model

    Correct this machine's local speed prediction using a real Ollama-linked model — never uploaded.

  • setting catalog-trust --manifest-url URL --public-key KEY—Default: unset

    Require future recommendation downloads to pass Ed25519 signature verification.

  • setting catalog-status—Default: —

    Show the current signed-catalog trust and rollback state.

  • setting catalog-rollback—Default: —

    Restore the most recent different recommendation snapshot.

03 / 06

Examples

From a plain search to something you'd put in a script.

Open the interactive menu covering every setting below.

$ omm setting

Show the current color theme.

$ omm setting theme

Show all three outbound-data policies at once.

$ omm setting upload

Turn anonymous usage stats off and discard anything already queued.

$ omm setting upload usage --disable

Show signed-catalog trust and rollback state.

$ omm setting catalog-status

04 / 06

A real run

Real bare omm setting upload run, 2026-09-01, against a throwaway OMM_HOME — the three real default policies on a machine that has never been asked, verbatim including the hint line under the table. Table borders are dropped for the web, as everywhere on this page set.

06 / 06

If something goes wrong

Every message below is one this command actually prints. Find yours, read why it happened, then do the last line.

  1. Choose only one of --enable, --disable, or --ask.
    why
    omm setting upload benchmark and omm setting upload crash each take exactly one policy flag; this run passed more than one at once.
    what to do
    Pass only one of --enable, --disable, or --ask.
    source
    src/omm/cli.py:6454, :6489
  2. Set an endpoint with `omm setting telemetry --endpoint` before enabling uploads.
    why
    Benchmark uploads have nowhere to go until a telemetry endpoint is configured, so --enable refuses rather than silently enabling a policy that can never send.
    what to do
    Run omm setting telemetry --endpoint URL first, then re-run the --enable.
    source
    src/omm/cli.py:6459-6460
  3. The signed catalog manifest must use HTTPS.
    why
    Signed-catalog verification has to happen over a connection that can't be tampered with in transit — an HTTP manifest URL defeats the point of requiring a signature at all.
    what to do
    Use an HTTPS manifest URL.
    source
    src/omm/cli.py:6828
  4. --policy must be ask, block, or observe.
    why
    Memory Guard's policy only has three real values, and this run passed something else.
    what to do
    Use ask, block, or observe.
    source
    src/omm/cli.py:6602

Still stuck? Open an issue with the exact message you saw.

All commands