OwnLLM Docs
CLI

update

Self-update the OwnLLM CLI on the stable or beta channel.

ownllm update                         # stable channel
ownllm update --channel beta

Hits /api/cli-updates/manifest/<platform>/<arch>/<current>, compares your installed version against the channel pin, and prints the recommended action. When a newer version is available it:

  1. Downloads the signed tarball.
  2. Verifies the minisign signature.
  3. Atomically swaps the running binary with the new one.
  4. Suggests ownllm restart if a daemon is running so subprocesses pick up any contract changes.

Channels

ChannelWhen to use it
stable (default)Production, anything paired to a paying tenant.
betaDogfooding the next release. Patches land here first.

You can switch channels at any time:

ownllm config set update_channel beta

The update_channel key (~/.config/ownllm/config.toml) is what update reads if you don't pass --channel explicitly.

Manifest

The update manifest the CLI consumes is shaped like:

{
  "version": "0.5.0",
  "released_at": "2026-04-25T10:11:12Z",
  "tarball_url": "https://github.com/impulse-studio/ownllm/releases/download/v0.5.0/ownllm-darwin-arm64.tar.gz",
  "minisig_url": "https://github.com/impulse-studio/ownllm/releases/download/v0.5.0/ownllm-darwin-arm64.tar.gz.minisig",
  "release_notes_url": "https://github.com/impulse-studio/ownllm/releases/tag/v0.5.0"
}

The site emits one manifest per (platform, arch, channel) triple. The platform / arch are inferred from uname -sm on Unix and PowerShell environment variables on Windows.

Air-gapped / offline

Self-update needs egress to ownllm.app. On an air-gapped host, download the tarball and run minisign verification by hand — see the manual install steps for your platform.

Rollback

If an update bricks something:

ownllm --version
ownllm update --channel stable     # in case you bumped to beta

Or grab a prior tarball from the releases page and overwrite the binary by hand.

On this page