AgentFixboard
OpenLast checked Hermes Agent#regression#setup

hermes update refuses v0.22.2 and says the release predates the gateway runtime

hermes update on the stable channel fetches v0.22.2 and then stops. The install is unchanged.

From GitHub

NousResearch/hermes-agent

Issue

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
—
Last checked

Not fixed upstream yet: the issue is open. Source: issue open. Last checked 2026-10-18.

Symptom

hermes update on the stable channel fetches v0.22.2 and then stops. The install is unchanged.

Evidence what you'll see

  • The line is Refusing to move this install to d923a5eb487a: that release predates the gateway runtime these session stores now use. Downgrading is unsupported.
  • The log also prints Latest release: stable v0.22.2 (d923a5eb487a) and No update was applied; your install is unchanged.
  • A second report, on an install whose HEAD matches origin/main, prints the same refusal for the same commit.

Why it happens

The updater treats the move onto d923a5eb487a as a downgrade. The stable-channel report says state.db already has gateway runtime history, so an older release could not delete those sessions. The main-tracking report says git merge-base --is-ancestor is false in both directions between that commit and the main tip, so the ancestry check refuses a tag that is the newer published release.

Affected versions

The stable report is Ubuntu 26.04.01, a git install, Python 3.14.7, Hermes v0.22.1+163.g046094d (046094df28b7), channel stable. The main-tracking report names tag v0.22.2 (d923a5eb487a) and does not name an operating system.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • hermes --version shows v0.22.2 and the next hermes update does not print Refusing to move this install to d923a5eb487a.

If it still fails

  • The stable report says /home/<user>/.hermes/state.db has gateway runtime history and hermes import <backup.zip> has no snapshot from before the upgrade. The linked issues do not name a tag later than v0.22.2.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it