ommv0.2.148

omm recommend

Rank models by a predictor trained on real install telemetry — falling back to static rules when the trained model can't be fetched — and offer to install the top pick.

01 / 06

Overview

Reach for recommend when you don't already know what to install: it scans this machine, ranks candidates by predicted speed and how much of the safe memory budget they'd use, and — outside --json — walks you through picking one and installs it directly. --json is read-only: it prints the ranked list and installs nothing, which is what makes it safe to script. --yes skips the picker and installs whatever ranked first.

02 / 06

Options

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

  • --json—Default: off

    Print the ranked candidates as JSON and install nothing.

  • --yes, -y—Default: off

    Skip the interactive picker and install the top-ranked candidate immediately.

  • --quiet, -q—Default: off

    Suppress background status or hint lines. Errors and the ranked result still print.

  • --no-color—Default: off

    Disable colored terminal output.

  • --help—Default: off

    Print recommend's usage and options, then exit.

03 / 06

Examples

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

Interactive — ranks candidates, then walks you through picking one to install.

$ omm recommend

Read-only — prints the ranked list, installs nothing.

$ omm recommend --json

Non-interactive — installs the top-ranked candidate without asking.

$ omm recommend --yes

04 / 06

Recorded CLI run

Command recorded in this video

omm recommend --json --no-color

exit code: 0 · outcome: completed

Read-only capture in an isolated environment with outbound network access blocked.

Open the exact real-process transcript (.txt)

Extended documented terminal example

The hardware panel and table header are a real omm recommend capture, 2026-08-24, this dev machine. The two model rows are a format-accurate reconstruction from a real omm recommend --json run the same day — the arrow-key picker draws its rows directly to the terminal, so they never appear in plain captured output. A fresh run reflects this machine's live memory budget and the current candidate catalog.

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. No model is predicted to run on this hardware.
    why
    Every candidate the trained predictor ranked came back under the minimum usable speed for this hardware.
    what to do
    This machine likely needs a smaller model than anything currently in the trained catalog — try omm search for something specifically small, e.g. a 1-3B model.
    source
    src/omm/cli.py:2913
  2. No model in the current rules fits this hardware.
    why
    The trained model wasn't available, so recommend fell back to the static rules — and even those found nothing that fits the memory this machine has free.
    what to do
    Close other applications to free memory and try again, or search for a smaller model directly.
    source
    src/omm/cli.py:2949

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