omm

omm list

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

01 / 06

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 / 06

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 / 06

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 / 06

A real run

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

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. --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.

All commands