---
title: "Installation"
description: "Install antiburn on macOS, Windows, or Linux, what the installer verifies, and how to uninstall it."
url: "https://antiburn.ai/docs/getting-started/installation/"
---
## Platform support

| Platform                                                     | Support                                         |
| ------------------------------------------------------------ | ----------------------------------------------- |
| macOS 13 or later (Apple silicon and Intel)                  | Supported                                       |
| Windows 11 (x86-64)                                          | Supported                                       |
| Linux, mainstream x86-64 desktops with a system tray         | Supported (Debian/APT packages, or an AppImage) |
| macOS 12 or earlier, Windows 10, Linux without a system tray | Not supported                                   |

antiburn is a tray application - a Linux desktop with no system tray (and no AppIndicator host) can't run it.

## Install

macOS or Linux:

```sh
curl -fsSL https://antiburn.ai/install.sh | sh
```

Windows 11, in PowerShell:

```powershell
irm https://antiburn.ai/install.ps1 | iex
```

Manual packages (DMG, `.deb`, AppImage, and the Windows installer) are available from the [latest GitHub release](https://github.com/antiburn/antiburn/releases/latest) if you'd rather not run a script.

### What the installer verifies

Both installers download the exact release asset for your platform plus its `SHA256SUMS` file, and refuse to install unless the downloaded file's checksum matches exactly. On macOS, the installer also verifies the app bundle's code signature (`codesign --verify`), that Gatekeeper accepts it (`spctl --assess`), and that its bundle identifier is `ai.antiburn.desktop` before it touches `/Applications`.

Setting `ANTIBURN_VERIFY_ATTESTATION=1` in the environment adds a further check: the installer calls `gh release verify-asset` (the GitHub CLI must be installed and authenticated) to verify the release's build attestation before installing.

### What each installer does

- **macOS** - downloads the `.dmg`, mounts it read-only, verifies the app inside it, then copies it into a staging directory under `/Applications`, verifies it again, and only then swaps it into place at `/Applications/antiburn.app`. If a previous install exists there, it's moved aside first and restored automatically if the swap fails partway through, so a failed install doesn't leave you without a working copy. Installing to `/Applications` when your account can't write there will prompt macOS for an administrator password.
- **Linux (Debian/APT)** - if `apt-get` and `dpkg-deb` are available, the installer downloads the `.deb`, checks its package name, architecture, and version, and installs it with `apt-get install --allow-downgrades`.
- **Linux (AppImage)** - otherwise, the installer downloads the AppImage to `~/Applications/antiburn.AppImage` and links it from `~/.local/bin/antiburn`, backing up and atomically swapping any existing install so a failed download or interrupted install rolls back cleanly.
- **Windows** - downloads and verifies the `.exe` installer, then runs it passively (`/P /R`, no prompts) and confirms `antiburn.exe` landed under `%LOCALAPPDATA%\antiburn\`. The Windows installer isn't Authenticode-signed yet, so SmartScreen may warn on first run.

## Pinning a version

Both installers default to the latest release, resolved from GitHub. To install a specific version instead:

```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
```

The shell installer also accepts a `--version` flag directly (`install.sh --version 0.4.0`) if you've downloaded the script rather than piping it into `sh`.

## Where antiburn lands

| Platform         | Location                                                                |
| ---------------- | ----------------------------------------------------------------------- |
| macOS            | `/Applications/antiburn.app`                                            |
| Windows          | `%LOCALAPPDATA%\antiburn\antiburn.exe`                                  |
| Linux (APT)      | Installed system-wide as the `antiburn` package                         |
| Linux (AppImage) | `~/Applications/antiburn.AppImage`, linked from `~/.local/bin/antiburn` |

Once it's installed, antiburn lives in your menu bar or system tray - it has no Dock icon and opens no window on launch (other than first-run setup; see [First run and onboarding](/docs/getting-started/first-run/)).

## Uninstalling

antiburn doesn't ship an uninstall command, but removing it is the same as removing any other app for your platform:

- **macOS** - quit antiburn, then move `/Applications/antiburn.app` to the Trash.
- **Linux (APT)** - `sudo apt remove antiburn` (or `apt purge antiburn` to also remove its package configuration).
- **Linux (AppImage)** - delete `~/Applications/antiburn.AppImage` and the `~/.local/bin/antiburn` link.
- **Windows** - Settings → Apps → Installed apps → antiburn → Uninstall.

Removing the app leaves its local data behind. antiburn keeps everything it stores under the operating system's application data directory for its bundle identifier, `ai.antiburn.desktop` - while antiburn is still installed, Settings → About shows the exact path. If you want to remove that data too, delete that folder after uninstalling the app itself. antiburn never touches your coding agents' own session files, whichever way you uninstall it - those stay exactly where your agents put them.