Updating Archon

Use the same method you used to install Archon. Read the release notes before updating. Let active workflows finish and stop any running Archon server before replacing its executable or source checkout. Restart the server afterward so the console and new runs use the updated version.

A release binary checks that each installed provider matches its own version. After a Homebrew or quick-installer update, reinstall the providers you use (the quick installer asks; Homebrew does not):

archon provider add claude codex   # the providers you use

Until you do, a run that needs one fails before it starts and prints this command. archon doctor lists each provider’s installed version. Docker and source installs run providers from source and skip this step.

Homebrew

brew update
brew upgrade archon
archon version

Quick installer

Re-run the installer to download and replace the executable with the latest release.

macOS / Linux

curl -fsSL https://archon.diy/install | bash
archon version

Windows (PowerShell)

irm https://archon.diy/install.ps1 | iex
archon version

Docker

For the release image shown in the installation guide, pull the new image before starting another container:

docker pull ghcr.io/coleam00/archon:latest
docker run --rm -v "$PWD:/workspace" ghcr.io/coleam00/archon:latest version

For a long-running container, stop and recreate it using the same volumes, environment, and ports as the original container. Restarting an existing container does not change its image. Keep your data volumes.

The repository’s Docker Compose deployment builds from source. Follow its update instructions, retaining the profiles you used for deployment; rebuilding and recreating the app loads the updated source.

From source

In your Archon checkout, first check for local changes:

git status

Commit or stash your changes before updating. The main branch contains releases; dev is the working development branch.

git switch main
git pull --ff-only
bun install --frozen-lockfile
bun run cli version

If you serve the console from source, rebuild it with bun run build:web before restarting your server.

Update notices

Compiled CLI installs check for updates in the background during workflow run and workflow resume. When fresh release data is available, they print update instructions to stderr at most once every 24 hours, even when the command fails. --quiet and --json suppress this notice. An unavailable network or stale cache does not delay the command.

The console shows a banner when a newer release is available. Dismissing it is remembered in your browser for that release; a later release shows the banner again.