omm

omm search

Search omm's curated catalog, your cached candidates, and HuggingFace and ModelScope, all in one query.

01 / 06

Overview

Reach for search before install: it is how you find the exact repo reference or numeric index that install accepts. Results are grouped by model family, numbered in the terminal, and models this hardware is predicted not to run print in red instead of being hidden — unless --skip-unfit says otherwise. The numbers search prints are only valid in the terminal that ran it: the next search or list run renumbers everything.

02 / 06

Options

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

  • <query>—Default: required

    The text to search for. Matched against the curated/cached catalog first, then HuggingFace and ModelScope.

  • --skip-unfit—Default: off

    If this hardware is predicted not to run a model, omit it from the results instead of listing it in red.

  • --limitNDefault: no limit

    Show at most this many results.

  • --providercurated | huggingface | modelscopeDefault: all three

    Only show results from this source: curated (omm's built-in/cached catalog, not a real host), huggingface, or modelscope.

  • --skip-ms—Default: off

    Don't query ModelScope. Its results need one extra network request per candidate repo, which can noticeably slow down search.

  • --json—Default: off

    Print structured JSON to stdout instead of a formatted list — the only thing written to stdout, so it's safe to pipe.

03 / 06

Examples

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

Plain search — results grouped by family, numbered for the install command that follows.

$ omm search qwen

Cap the result count.

$ omm search qwen --limit 3

Drop anything predicted not to run on this machine instead of showing it in red.

$ omm search qwen --skip-unfit

Only HuggingFace results, skipping the curated catalog and ModelScope.

$ omm search qwen --provider huggingface

JSON output piped to jq — safe because --json is the only thing search writes to stdout.

$ omm search qwen --json | jq '.[0]'

04 / 06

A real run

Real omm search qwen capture, 2026-08-24, this dev machine, trimmed to the first six of 60 results for length. HuggingFace and ModelScope rankings change constantly, so a fresh run will list different repos.

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. --provider must be one of: curated, huggingface, modelscope (got 'bogus').
    why
    --provider only accepts three values, and this run passed something else.
    what to do
    Use one of curated, huggingface, or modelscope.
    source
    src/omm/cli.py:6320-6323
  2. --skip-ms conflicts with --provider modelscope.
    why
    --skip-ms says don't query ModelScope; --provider modelscope says show only ModelScope results. Those cancel each other out.
    what to do
    Drop --skip-ms, or point --provider at curated or huggingface instead.
    source
    src/omm/cli.py:6326
  3. No models found matching 'zzzznonexistentmodelxyz'.
    why
    None of the curated catalog, your cached candidates, HuggingFace, or ModelScope had anything matching this query.
    what to do
    Try a shorter or differently spelled query — search matches by name, not by exact repo ID.
    source
    src/omm/cli.py:6362

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

All commands