--- title: "Updating antiburn" description: "How antiburn's in-app updater checks GitHub Releases, what it does automatically, and how to reinstall a specific version." url: "https://antiburn.ai/docs/getting-started/updating/" --- ## The in-app updater Release builds of antiburn can check GitHub Releases for a newer version. It's the only part of the app that talks to a service of ours besides the model-pricing catalog and (if enabled) anonymised analytics - and it never depends on that connection: antiburn works exactly the same whether the check succeeds, fails, or never runs. The check itself sends nothing about you, your machine, or your sessions - it only asks whether a newer release exists. ## Automatic updates **Install updates automatically** is on by default, in Settings → About → Updates. With it on, antiburn: - checks once about 30 seconds after launch, and then every 6 hours; - skips a scheduled check while the popover is open, retrying again shortly after; - downloads and verifies the new version's signature against the public key built into your copy of antiburn, then installs it and restarts the app automatically once installation succeeds. Turn the switch off and antiburn will still tell you when an update is available (via Settings → About), but won't download or install anything without your say-so. ## Checking and installing by hand Settings → About → Updates shows the current state - up to date, a version available, downloading (with a progress bar once the server reports a size), verifying and installing, or installed and waiting for a restart - and lets you trigger a check at any time regardless of the automatic-update setting. ## Platform differences - **Linux AppImage** releases can update themselves in place through the in-app updater, the same as macOS and Windows. - **Linux Debian packages** are install-only: the in-app updater won't touch a `.deb` install, and you reinstall by downloading and running the next release's package, or by rerunning the install script (see below). - **Development builds carry no updater at all** - only official release builds register the updater plugin, so a build from source never checks for or installs updates. ## Reinstalling a specific version To roll back, or to pin a particular release rather than waiting for the automatic updater, rerun the install script with a version pinned: ```sh ANTIBURN_VERSION=0.4.0 curl -fsSL https://antiburn.ai/install.sh | sh ``` ```powershell $env:ANTIBURN_VERSION = "0.4.0"; irm https://antiburn.ai/install.ps1 | iex ``` This downloads and verifies that exact release the same way the first install did - checksum-verified, and code-signature-verified on macOS - and replaces your existing installation. See [Installation](/docs/getting-started/installation/) for what each installer checks and where antiburn lands on each platform.
Updating antiburn
How antiburn's in-app updater checks GitHub Releases, what it does automatically, and how to reinstall a specific version.
The in-app updater
Release builds of antiburn can check GitHub Releases for a newer version. It’s the only part of the app that talks to a service of ours besides the model-pricing catalog and (if enabled) anonymised analytics - and it never depends on that connection: antiburn works exactly the same whether the check succeeds, fails, or never runs.
The check itself sends nothing about you, your machine, or your sessions - it only asks whether a newer release exists.
Automatic updates
Install updates automatically is on by default, in Settings → About → Updates. With it on, antiburn:
- checks once about 30 seconds after launch, and then every 6 hours;
- skips a scheduled check while the popover is open, retrying again shortly after;
- downloads and verifies the new version’s signature against the public key built into your copy of antiburn, then installs it and restarts the app automatically once installation succeeds.
Turn the switch off and antiburn will still tell you when an update is available (via Settings → About), but won’t download or install anything without your say-so.
Checking and installing by hand
Settings → About → Updates shows the current state - up to date, a version available, downloading (with a progress bar once the server reports a size), verifying and installing, or installed and waiting for a restart - and lets you trigger a check at any time regardless of the automatic-update setting.
Platform differences
- Linux AppImage releases can update themselves in place through the in-app updater, the same as macOS and Windows.
- Linux Debian packages are install-only: the in-app updater won’t touch a
.debinstall, and you reinstall by downloading and running the next release’s package, or by rerunning the install script (see below). - Development builds carry no updater at all - only official release builds register the updater plugin, so a build from source never checks for or installs updates.
Reinstalling a specific version
To roll back, or to pin a particular release rather than waiting for the automatic updater, rerun the install script with a version pinned:
ANTIBURN_VERSION=0.4.0 curl -fsSL https://antiburn.ai/install.sh | sh
$env:ANTIBURN_VERSION = "0.4.0"; irm https://antiburn.ai/install.ps1 | iex
This downloads and verifies that exact release the same way the first install did - checksum-verified, and code-signature-verified on macOS - and replaces your existing installation. See Installation for what each installer checks and where antiburn lands on each platform.