Skip to the content

Check for and verify AgentGarm updates

Find the newest AgentGarm release, check its signature and checksums before you run it, never go back to an older one, and upgrade in place.

Find out whether a newer release is out, check its minisign signature and SHA-256 checksums before anything runs, refuse a version older than the one you have, and install it over the old one with a restart. AgentGarm does not update itself: nothing is downloaded or installed until you do it. The first release is not out yet, so until then there is nothing to download or verify.

1. Find the newest release

The download page names the newest release, its date, whether it is a pre-release and which platforms are code-signed, and lists any withdrawn release with the reason. Once a release is out, the site also serves /download/latest.json, a pointer with the newest version and tag. The pointer is not signed and proves nothing: use only its version, then fetch and check that release's own files below.Until the first release is published, the page says so and none of these files exist.

curl -fsS https://agentgarm.com/download/latest.json

2. Verify the download before you run it

Every release carries SHA256SUMS over its files and a minisign signature over it by the release key. Check the signature, then your file's SHA-256 against the list, as verify a download shows on each platform; if either check fails, do not run the file. The release key is published with the first release. A key taken from this site cannot catch the site itself being changed, so compare it with a copy from somewhere else.

Each release also has feed.json and feed.json.minisig, beside SHA256SUMS in the same release's download folder, signed the same way: its version, tag and commit, which platforms are code-signed, whether it is a pre-release, and every file's SHA-256. A good signature says the release is ours, not that it is the newest or has not been withdrawn. minisign prints the signature's trusted comment, agentgarm v<version> feed.json: check that its version is the one you downloaded.

minisign -Vm SHA256SUMS -p release-feed.pub
minisign -Vm feed.json -p release-feed.pub
sha256sum -c SHA256SUMS --ignore-missing

3. Never go back to an older version

A validly signed old release still verifies, so the version is your check: refuse one below the highest you have installed, and check that the version in feed.json is the one you meant to fetch. Whoever controls the site could keep showing an old release as the newest, since neither the pointer nor the feed expires, and the withdrawn flag on the download page is not signed. Releases published as signed TUF metadata will add expiry and signed withdrawal; that signing has not been set up yet.

4. Install the new release over the old one

No package runs a script, so an upgrade is two moves: install the new package over the old one, then restart the services. On a root install, run sudo agentgarmd install before the restart when the release notes say its service unit changed. Without root, unpack the tarball into its own directory, put its bin first on your PATH, run agentgarm install --user from it and restart. Your policies, the audit log and the store carry over; each install page has the commands for its platform, such as without root.

sudo apt install ./agentgarm_X.Y.Z-1_amd64.deb
sudo systemctl restart agentgarmd
systemctl --user restart agentgarm-session   # as each user
tar -xzf agentgarm-X.Y.Z-<target>.tar.gz -C ~/.local/opt
export PATH="$HOME/.local/opt/agentgarm-X.Y.Z-<target>/bin:$PATH"   # and in your shell profile
agentgarm install --user
systemctl --user restart agentgarmd agentgarm-session

5. Check that the new release is running

Until the services restart, the old daemon keeps running, and agentgarm status and agentgarm doctor say it needs a restart. The restarted agentgarmd points the agents' hooks at the new release by itself; agentgarmd hooks status says stale for an agent it has not reached yet.

agentgarm status
agentgarm doctor
sudo agentgarmd hooks status claude-code

Checked by the walk: these commands ran as written on a no-root Linux install.

See also

Check that protection is on

See whether AgentGarm's services are up, what assurance level each agent session has and why, and what to do about a bypass alert.

6. Verify a TUF repository or mirror

agentgarm update verify checks a TUF repository directory against a root you pin, the way agentgarmd will before it activates anything from one: each newer root signed by the threshold of the old and the new, then the timestamp, snapshot and targets with their signatures, versions and expiry. Expired metadata is a freeze and fails the check, and a snapshot that lowers the targets version is refused as a rollback. --target also checks one file's length and SHA-256; on success it prints Repository verified with the root version and the targets. AgentGarm's own releases are not yet published as TUF metadata, so today this is for a repository or mirror you sign yourself.

agentgarm update verify --repo <dir> --root <root.json> --target <name>