omm

omm list

Show every model installed via omm, its size, and which runners it's linked into.

01 / 07

Overview

Reach for list to see the current state of the hub — what's on disk, how big it is, and where it's linked. The numbers it prints, like search's, are only valid in the terminal that ran it: install, uninstall, info, and upgrade all accept that number in place of a name.

02 / 07

Options

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

  • --engineNAMEDefault: every engine

    Only show models linked into this engine.

03 / 07

Examples

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

Every model omm has installed.

$ omm list

Only the ones linked into Ollama.

$ omm list --engine ollama

The same table as JSON.

$ omm list --json

04 / 07

A real run

Real omm list capture, 2026-08-24, this dev machine.

06 / 07

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. --engine must be one of: anythingllm, jan, koboldcpp, lmstudio, mstystudio, ollama, textgenwebui (got 'bogus').
    why
    --engine only accepts a real engine key, and this run passed something else.
    what to do
    Use one of the seven listed in the message — anythingllm, jan, koboldcpp, lmstudio, mstystudio, ollama, or textgenwebui.
    source
    src/omm/cli.py:909-911

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

07 / 07

CLI reference

Exactly what omm list --help prints, exported from the CLI source.

Usage

omm list [OPTIONS]

Also accepted as: ls

Options

  • --engine <str>Default: —

    Only show models linked into this engine.

Shared flags

Every omm command also accepts --json, --no-color, --quiet, -q, --yes, -y, so they are listed here once instead of on each command.

Exported from omm 0.3.101.

All commands