omm

omm fit

Show whether a model — installed or not — fits this machine's memory right now, as a bar over what other apps are using.

01 / 06

Overview

Reach for fit when you want a live answer, not a cached one: unlike the fit check inside install, this reads memory availability at the moment you run it, so the same model can read differently five minutes later if other apps opened or closed. It works on models that aren't installed yet too, as long as their size can be resolved from the provider.

02 / 06

Options

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

  • <name>—Default: required

    An installed model's filename, a curated name, or a repo reference whose size the provider reports.

03 / 06

Examples

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

The fit card for an installed model.

$ omm fit qwen2.5-0.5b-instruct-q4_k_m.gguf

The same numbers as JSON — useful in a script's fit check before installing.

$ omm fit qwen2.5-0.5b-instruct-q4_k_m.gguf --json

Works on a model that isn't installed yet, as long as its size is known.

$ omm fit mistral-7b-instruct-q4

04 / 06

A real run

Real omm fit qwen2.5-0.5b-instruct-q4_k_m.gguf 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. Could not determine the size of oversized-405b-q4_k_m.gguf (not installed, and the provider did not report a file size).
    why
    The model isn't installed, and its provider didn't report a file size fit could use to estimate memory — this happens for some direct-URL or unusual repo references.
    what to do
    Install it (fit's own check runs first, so nothing downloads if it clearly won't fit) or search for it by name to find a reference with size metadata.
    source
    src/omm/cli.py:5608-5611
  2. --json has no effect on `omm fit` - ignoring it.
    why
    This is a real, verbatim warning omm itself prints — fit's own code does branch on --json and prints structured output correctly (see the captured JSON example above); the warning is a known mismatch in the flag-handling decorator's own bookkeeping, not a sign the flag actually failed.
    what to do
    Nothing to do — the JSON output is correct regardless of this warning.
    source
    src/omm/cli.py global_flags decorator

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

All commands