omm

omm update

Reinstall omm from the latest source on the current update channel, and refresh its recommendation and rules data.

01 / 06

Overview

Reach for update to get the newest omm — it pulls from whichever channel omm setting version has selected (stable by default, or beta), and does nothing destructive if you're already current, just refreshing the recommendation and rules data instead. A package-managed install (Homebrew, pipx from PyPI) prints its own manager's upgrade command instead of touching anything, since update only knows how to manage a Git-source install.

02 / 06

Options

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

    03 / 06

    Examples

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

    Update to the latest commit on the current channel.

    $ omm update

    Same update, without the progress output.

    $ omm update --quiet

    04 / 06

    A real run

    Format-accurate reproduction of the real up-to-date message (src/omm/cli.py:2536) — not a literal run, since update reinstalls omm itself when a newer commit exists, and this page won't trigger that on a real machine. The version and commit shown are representative, not this specific dev machine's.

    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. Update failed:
      why
      The underlying git pull or pipx reinstall step failed — the message includes that command's own stderr for the actual reason.
      what to do
      Read the included error for the specific cause (network, permissions, a dirty local checkout), fix that, and retry.
      source
      src/omm/cli.py:2542-2544

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

    All commands