omm

omm engine install

Install a local AI runner program directly — Ollama, LM Studio, and the rest of the seven omm links into — without going through the full setup wizard.

01 / 07

Overview

Reach for engine install when you want one more runner without repeating the whole setup wizard — after installing it, omm scan or omm link will pick it up and start linking models into it like any other runner. With no argument it shows the same checklist setup does; with an engine key it installs that one directly, using whichever package manager is automated for it on this platform (see the runner coverage table on the landing page for which ones that is, per OS).

02 / 07

Options

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

  • [engine]—Default: none — interactive checklist

    Which runner to install: ollama, lmstudio, jan, anythingllm, mstystudio, textgenwebui, or koboldcpp. Left out, shows an interactive checklist instead.

03 / 07

Examples

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

Interactive checklist, same as the setup wizard's.

$ omm engine install

Install one runner directly.

$ omm engine install lmstudio

Install without any confirmation prompts.

$ omm engine install ollama --yes

04 / 07

A real run

Real omm engine install lmstudio run, 2026-08-25, this dev machine — a genuine Homebrew-cask install, not a stand-in. The very long percentage-by-percentage download output has been trimmed to its start and end; everything else is verbatim, including the real lms daemon up hint LM Studio's own installer prints. LM Studio is now actually installed on this machine as a result.

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. LM Studio is already installed.
    why
    This exact runner is already installed — engine install has nothing to do.
    what to do
    Nothing to do. Use omm scan to confirm what's already installed.
    source
    src/omm/cli.py:1109-1111
  2. engine must be one of: anythingllm, jan, koboldcpp, lmstudio, mstystudio, ollama, textgenwebui (got 'bogus').
    why
    The engine key only accepts one of the seven real runner keys, and this run passed something else.
    what to do
    Use one of the seven listed in the message.
    source
    src/omm/cli.py:1104-1108

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

07 / 07

CLI reference

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

Usage

omm engine [OPTIONS] COMMAND [ARGS]...

Options

This command takes no options of its own.

Sub-commands · 5 sub-commands

omm engine doctor

Read-only engine diagnostics and the next step for missing components.

omm engine doctor [OPTIONS] [engine]

This command takes no options of its own.

omm engine install

Install a local AI runner program (Ollama, LM Studio, etc.).

omm engine install [OPTIONS] [engine]

With no argument, interactively pick from a checklist. With an engine key, install that one runner directly.

This command takes no options of its own.

omm engine status

Show installation, package version, and local API state separately.

omm engine status [OPTIONS] [engine]
  • --api, --no-apiDefault:

    Check local API reachability; never start a server.

omm engine uninstall

Remove an engine package without deleting the OMM model hub.

omm engine uninstall [OPTIONS] {engine}
  • --dry-runDefault: —

    Show the package command without executing it.

omm engine update

Update one engine through its identified package manager.

omm engine update [OPTIONS] {engine}
  • --dry-runDefault: —

    Show the package command without executing it.

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