Help
Updating Akev
While its window or web UI is open, Akev looks for a new release at most once a day, and tells you when there is one. Nothing is downloaded or installed until you say so.
The update check
By default, while the UI is open, Akev fetches a small file, latest.json, from the
GitHub releases of the project, at most once a day,
to see whether a newer version is out. That request carries nothing but what any download
from GitHub does: your IP address, and a User-Agent that names the Akev version. It is the only
request Akev makes on its own; it has no telemetry. Headless runs (akev capture, CI) never
check.
To turn it off, switch off Check for updates automatically under Settings → About →
Updates. Check now there, and akev update on the command line,
check when you ask. A new version shows as Update available in the status bar.
When a newer release is out, the desktop app offers to update. It downloads and installs the update only after you click Update, and it verifies the update package's signature before installing it. You can also update by hand, as below.
Find new versions
Every release is published on GitHub with its
release notes, all packages and a SHA256SUMS file. To hear about new releases, watch the
repository there (Watch → Custom → Releases). The download page links the
current release.
To see which version you have, open Settings → About in the app, or run akev version.
Update the desktop app
Click Update when the app offers it, or update by hand: quit Akev, then install the new version over the old one, with the same kind of package you installed before:
| Package | How to update |
|---|---|
macOS .dmg |
Open it and drag Akev into Applications. Choose Replace when Finder asks. |
macOS .app.tar.gz |
Extract it and replace Akev.app with the new one. |
Windows -setup.exe |
Run the new installer. |
Windows .msi |
Run or deploy the new .msi. |
| Linux AppImage | Download the new .AppImage, make it executable (chmod +x) and delete the old one. |
Debian, Ubuntu .deb |
sudo apt install ./Akev_<version>_amd64.deb |
Fedora, RHEL .rpm |
sudo dnf install ./Akev-<version>-1.x86_64.rpm |
The .deb and .rpm packages don't add a package repository, so apt upgrade and
dnf upgrade don't update Akev. Install the new package file as shown.
Update the command-line tool
Stop Akev (akev stop, or Ctrl+C where it runs), and close MCP clients that run akev mcp.
Extract the new archive and put its akev binary in place of the old one.
Keep the same location, so scripts and MCP clients that use its full path keep working.
akev version then shows the new version.
The desktop packages don't include the akev command. If you use it next to the desktop app,
for MCP for example, update it as well.
Update the Docker image
Pull the new version and recreate the container with the same data volume:
docker pull ghcr.io/akevdev/akev:<version>
docker rm -f akev
docker run -d --name akev -p 8000:8000 -p 45456:45456 \
-e AKEV_TOKEN -v akev-data:/data ghcr.io/akevdev/akev:<version>AKEV_TOKEN must be set in your shell, as on the download page. The
akev-data volume holds the data directory (/data), so the new container keeps the
settings, rules and CA. Each release is tagged with its version (0.2.0) and with its minor
version (0.2).
What an update keeps
An update replaces the program only. What you set up lives in the data directory, outside the installation, and stays as it is:
- settings and rules (
settings.json,rules.json), - the CA certificate and its key (
ca.pem,ca.key), so browsers and devices that trust Akev keep trusting it, - your licence key (
license.json), saved sessions, protobuf schemas and WireGuard keys.
The data directory is ~/.local/share/akev on Linux, ~/Library/Application Support/akev on
macOS and %LOCALAPPDATA%\akev on Windows; Settings → About → Data directory shows it. The
desktop app and the akev command share it. The trial's start is recorded outside the
program too, so an update doesn't start it over (see
akev license trial).
If Akev can't read its settings or rules file, it moves the file aside (settings.json.bak,
rules.json.bak) and starts with defaults, so it still starts and the old file isn't lost.
Updates and Akev Pro
An update never touches your licence. Your key unlocks Pro in every release made up to its updates until date, and keeps doing so. A release made after that date runs as Free: nothing is deleted, and you can renew or go back to a release your key covers (every release stays on GitHub). See Updates.
Before you update, compare the dates. Settings → License shows Updates until and the
release date of the version you run; akev license status shows them as Covers and
This build. The date of each release is on
GitHub, and what changed is in the
changelog.
Verify a download
Each release lists the SHA-256 of every package in SHA256SUMS.
Verify your download shows how to check a file against it.