Skip to content

Updates in the console

The Versions page shows the running version, the latest release of the channel, the release notes, and installs updates. How to turn updates on and what an install does is in Update Prism. This page covers the source settings and the components list.

An official build updates from the public channel https://releases.prism.tm/prism/releases/latest with nothing to set up. The release host is not trusted with integrity: Prism installs a package only if its SHA256SUMS carries a valid signature by a release key built into the running binary. A build made from source with go build has no channel.

The source settings are folded under Advanced: custom source, mirror, token:

  • Add custom source sets another release API URL, written to [console] update_check_url in the console overlay. It is a …/releases/latest endpoint of Forgejo or Gitea, GitHub (https://api.github.com/repos/OWNER/REPO/releases/latest) or GitCode (https://api.gitcode.com/api/v5/repos/OWNER/REPO/releases/latest). The signature check stays the same: a release not signed by a built-in key is refused.
  • Once a source is set, the same control adds a download mirror: a prefix to which the original download URL is appended, for example https://ghfast.top/. A mirror cannot change a package unnoticed, because the archive is checked against the signed SHA256SUMS. A mirror without a source is refused.
  • Set token stores a read token for a private source, or a 1Password op:// reference when 1Password is configured, in Prism’s encrypted secrets store (<storage.dir>/provider-secrets/release-source.enc), not in config.toml and not in the browser. Prism sends it only to the source’s own address, never to a mirror, and the console does not show it again. [console] update_check_token_env (the name of an environment variable holding the token) also works; a token stored in the console wins.

Sources and mirrors are fixed when Prism starts, so a source or mirror added in the console works after the next restart.

The same values in config.toml:

[console]
update_check_url = "https://api.github.com/repos/OWNER/REPO/releases/latest"
update_mirrors = ["https://ghfast.top/"]
update_check_token_env = "PRISM_RELEASE_READ_TOKEN"
update_channel = "stable" # or "prerelease"

On a machine without access to the release host, download the platform archive, SHA256SUMS and SHA256SUMS.sig elsewhere and choose them under Offline installation. The signature and checksum checks are the same and need no network. Offline installation stays available when no release source is configured.

Below the version cards, Bundled release components lists the programs of the release that Prism can see (for example prism-service-agent next to the prism executable) with the version each one reports and the version Prism expects; a different version is highlighted. A component Prism cannot read says why. An update replaces the components that are installed and never adds one that is not.

The list also shows local model servers Prism routes to (self-hosted providers and providers on a local address): their address, whether their model list loads, the server version when the server reports one, and the models it serves now.

Every control that cannot work right now is disabled, with the reason next to it: no release source, no signature on the checked release, the latest version already installed, updates not enabled, no write access next to the executable, or an update still on probation. Prism refuses an install it could not foresee with a message (update_unavailable).