Local AI Toolkit

Updating and removing

Contents · Русская версия

On this page

Update

lai localai update

It downloads a release, verifies its signature, installs a new version directory and points the launcher at it. The paths written into your clients do not change — they point at the launcher, not at a version. It refuses while the broker has queued or running work; --wait waits for both to finish (up to 30 minutes), and --force installs the newest release even when it is not newer than the installed one. Downloading and verification leave other sessions available. The final drain and activation temporarily pause new submissions; retry those calls after the update finishes. Failure or cancellation restores normal admission. The launcher runs the updater from a temporary copy outside the installed version, so it can switch versions without waiting for its own process to exit. The command keeps showing progress and returns the updater’s final result; its temporary copy is removed when it exits. An older launcher without this handoff cannot update itself this way: use the installer from the published GitHub release for the first upgrade. Later upgrades can use localai update.

The update check is off by default, so the installation never goes looking for new versions on its own. To turn it on and set how often:

lai localai policy set --update-check on
lai localai policy set --update-check-interval-hours 24

Enabled update checks are anonymous by default. A private GitHub release can remain invisible to that lookup even when the installer succeeded through its GitHub CLI fallback. To explicitly allow the background check to use your existing GitHub CLI account after an anonymous lookup cannot find the release or its assets:

lai localai policy set --update-check-authentication GitHubCli

This does not turn checking on by itself. Authenticate GitHub CLI separately if needed; LocalAI does not request or store its token. The fallback fetches only release metadata, the manifest and its signature, and applies the same signature verification; it never downloads a package. Missing or revoked authentication is reported as authentication_unavailable, distinct from no_release. Changing the mode is noticed on the next broker check pass without a restart. Use --update-check-authentication Anonymous to return to anonymous-only access. The installer checkbox applies anonymous checking and resets this mode to Anonymous. Opt in again after an installer run if needed; a runtime-only update preserves the explicit mode.

update uses the published GitHub releases. To update client instructions as well, download the installer and package from the same release and run the installer with the relevant client selected. A runtime-only update preserves the existing client instructions.

Remove expired data, keep the product

lai localai prune            # drop stale generations, overlays, queue archive, old telemetry and old versions
lai localai prune --dry-run  # see what would go first

prune applies retention rules; it is not a complete data wipe. It keeps current indexes of active repositories and usage reports and telemetry still within their retention period. Preview the eligible data with --dry-run. To remove retained data as well, use the uninstaller below and select the data categories to delete.

prune also removes the record of a repository whose Git directory is gone, and of one that never published a generation and has not been updated for longer than the archive retention. A deleted worktree loses only its overlays, and a volume that cannot be reached leaves the record alone.

Remove it entirely

Local AI registers in Apps & features as Local AI Toolkit — remove it from there like any program. A wizard opens, and each part is decided separately, not with one “yes”:

Part What it is
Binaries, launcher, version pointer the uninstall proper
Repository indexes and their overlays hours of GPU work, and the documentation packages stored with them; only worth dropping if you are leaving for good
Runtime settings residency, updates, language servers — what a reinstall would otherwise honour
Queue, archive, quarantine, telemetry transient broker state; nothing to preserve
Everything else in the runtime root anything the installer does not recognise, listed by path
Git hooks per connected repository
Claude and Codex integration separately for each: unregister the MCP servers and remove the instruction block
Release signing keys always asked — never removed by default under any preset

There are ready-made presets: remove everything except the signing keys; remove the binaries, the transient state and anything unrecognised, keeping the indexes and settings; take Local AI out of Claude, Codex and the Git hooks without touching the runtime. A preset is just a set of boxes already ticked, and any of them can be changed.

Models stay. They belong to Ollama rather than to Local AI, and you may want them for something else. Remove those through Ollama.

The installation record stays too — deliberately, outside the runtime directory. It is the log of what installs did to this machine.


← What language it answers in · Contents · Impact evidence: C# pilot →