omm cleanup
Remove orphaned partial downloads left by an interrupted install, plus symlinks in runner model directories whose source .gguf was deleted outside of omm uninstall.
01 / 06
Overview
Reach for cleanup after an install was interrupted (network drop, Ctrl+C, a crash) and you want the partial download's disk space back without hunting for the file yourself, or when a runner's own model list shows an entry that no longer loads because the underlying .gguf was deleted by hand. It only ever touches incomplete, unregistered files and links that are already broken — never a finished, installed model still on disk. This is the same sweep omm contribute runs when it finishes.
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.
Clean up every leftover install file and broken runner symlink.
$ omm cleanupSame cleanup, without the progress output.
$ omm cleanup --quiet04 / 06
A real run
The partial-download half is a real omm cleanup run, 2026-08-25, against a throwaway OMM_HOME seeded with two genuine leftover .gguf.part files (the exact pattern _cleanup_incomplete_installs looks for) — cleanup found and deleted both. The broken-link count is a format-accurate reconstruction: reproducing it for real means corrupting this dev machine's real runner symlinks, which this page won't do. The counts are representative.
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.
Nothing to clean up.- why
- This is what cleanup prints on a healthy system with nothing to reclaim, which is most runs.
- what to do
- Nothing to do.
- source
- src/omm/cli.py
Still stuck? Open an issue with the exact message you saw.
All commands
- omm searchFind a model across the curated catalog, HuggingFace and ModelScope.
- omm installDownload a model into the hub and link it into every installed runner.
- omm runChat with an installed model — in the terminal for Ollama, or by opening the app for GUI runners.
- omm recommendGet a model suggestion ranked for this machine's hardware, with an offer to install it.
- omm contributeBenchmark models in a loop, uploading telemetry to improve recommend for hardware like yours.
- omm setupRe-run the hardware scan and runner-install checklist, any time.
- omm scanPrint this machine's hardware, detected runners, and models — no flags needed.
- omm tuneGet recommended context length, GPU offload, threads, and batch size for a model.
- omm fitSee whether a model fits this machine's free memory right now, installed or not.
- omm helpShow omm's own command summary, or the full reference with --all.
- omm importAdopt .gguf files sitting in other apps' model directories into the omm hub.
- omm uninstallRemove a model and clean up its symlinks and manifests. Alias: rm.
- omm listShow every model omm has installed and which runners each is linked into. Alias: ls.
- omm infoShow full detail — repo, version, size, links, run commands — for one installed model.
- omm upgradeRefresh installed models against their source — only re-downloads what's actually changed. Alias: up.
- omm linkRe-verify and repair every installed model's runner links, or link into a custom directory.
- omm verifyProve that an installed model actually loads and generates text on this machine.
- omm benchmarkLocal quality and speed smoke evidence for one or more installed models.
- omm updateReinstall omm from the latest source and refresh its recommendation data.
- omm settingView or change omm's settings — telemetry, outbound data, theme, update channel, and more.
- omm doctorDiagnose the omm install and Ollama links, read-only — no flags needed.
- omm engine installInstall one local AI runner program directly, skipping the setup checklist.
- omm logRead the local run log: what omm ran, when, and whether it worked.
- README — UsageEvery omm command, one line each.