Updating

One command. It verifies the download before it touches your installation, and leaves the old binaries behind so you can go back.

Already on 0.1.0? That build predates the update command, so it cannot update itself. Run the installer once — it replaces the old version in place — and every release after that can be updated with akili-code update.

curl -fsSL https://akilios.dev/install.sh | sh

Update

akili-code update

That downloads the current release for your platform, checks it against the release's SHA256SUMS, and replaces both binaries. If the checksum does not match, nothing is installed and your existing version is left exactly as it was.

Look without installing

akili-code update --check

Installed: 0.1.0
Available: 0.2.0

Run `akili-code update` to install it.

In the desktop app the same check is under Settings → Version → Check for updates. It is never automatic: an editor that phones home on launch and stalls on a slow connection is worse than one that is a version behind.

What happens to the old version

The binaries it replaces are renamed to akili-code.old and akili-code-ui.old beside the new ones (akili-code.exe.old on Windows), not deleted. If a release misbehaves you can rename one back. The next update replaces them, so there is never more than one previous version lying around.

On Windows, if you installed with the installer, the update also keeps Settings → Apps showing the version you are actually on.

Close the desktop app first if it is running. The CLI can update while a window is open, but that window keeps running the old code until you restart it — and on Windows a running .exe cannot be replaced at all, so the update will move it aside and the new one takes effect on next launch.

If your platform has no build yet

Releases are published per platform, and not every platform ships on every release. If yours is missing, the update says so plainly rather than failing oddly:

Version 0.2.0 has not been published for aarch64-apple-darwin yet.

Check the download page, which lists only builds that exist, or build from source.

Updating by hand

The installer is idempotent — running it again installs the current release over the old one:

curl -fsSL https://akilios.dev/install.sh | sh

On Windows, run the newer installer over the old one — it upgrades in place, keeps your install folder and settings, and works even if Akili Code is open (the running copy is moved aside and the new one takes effect next launch). The current installer is always at:

https://akilios.dev/download/akili-code-windows-setup.exe

A specific version's installer is in its folder, for example /download/0.1.14/akili-code-0.1.14-windows-x64-setup.exe. If you use the .zip instead, replace the two .exe files with the new ones.

To pin a specific version:

AKILI_VERSION=0.1.0 curl -fsSL https://akilios.dev/install.sh | sh

Verifying a download yourself

Every release publishes checksums beside the archives. The installer and akili-code update both check them for you, but if you are downloading by hand:

curl -O https://akilios.dev/download/<version>/SHA256SUMS
shasum -a 256 -c SHA256SUMS --ignore-missing

Your settings survive

Updating replaces two binaries and nothing else. Your providers, keys, budgets, policy and workflows live in your config directory and are untouched; so is everything in .akili-code/ inside each project — sessions, memory, audit log and usage history.

Installing somewhere else

The update writes to wherever the running akili-code lives. If you installed to a directory that needs elevation, run the update the same way you ran the install.

Variable	Effect
`AKILI_DOWNLOAD_URL`	Fetch releases from a mirror or an internal server instead of akilios.dev
`AKILI_INSTALL_DIR`	Where `install.sh` puts the binaries
`AKILI_VERSION`	Install a specific version rather than the current one

BackInstall → NextGetting started →