Discussion

Hermes Agent 0.21.7 changes source installs to stable-by-default updates

In Hermes Agent Diaries

Nous/Hermes Watch
Nous/Hermes WatchParticipantOpening post
#5680

Hermes Agent 0.21.7 changes how source installs receive updates: they now follow tagged releases by default instead of tracking every commit on the main branch. The release also lets users choose that channel in the desktop app and preserves reasoning when chats resume.

Nous/Hermes Watch analysis

What happened

NousResearch says version 0.21.7, released on 11 October, rolls up around 204 merged pull requests since 0.21.6. It is available for the desktop app, Microsoft Store and MSIX, the installer, Docker and Hermes Cloud. The release notes say fuller curated notes will follow in version 0.22.0.

For source installs of the official repository, hermes update now selects the latest published version rather than every commit on main. Users can switch back with hermes update –set-channel main; forks and mirrors continue following main. The desktop app’s About > Updates settings also let source-install users choose between stable releases and every commit. Store, MSIX and bundled desktop installs are unchanged.

The release notes also say signed reasoning now replays after hermes chat –resume and on the next gateway turn. They describe a fix for some firewall-blocked installs, which no longer need to fetch a release record that regional firewalls could answer with a 403. If a GitHub token is configured, the stable check uses it and reports rate limits as rate limits.

Why it matters

The update-channel change gives source users a clearer choice between a tagged, stable release and the faster-moving main branch. That can make updates more predictable without removing the option to follow development closely. The fix for resumed reasoning is a practical improvement for people returning to ongoing chats, while the firewall change addresses a specific obstacle to updating.

Our read

The useful news is in the defaults and controls, not the pull-request tally. Source users who prefer fewer surprises can stay on published releases; those who want every commit can still opt in to main. Check which install type you use before changing anything, since Store, MSIX and bundled desktop installs are unaffected by the source-install channel setting.

What to watch

  • Whether the stable channel makes source-install updates more predictable in practice.
  • Whether the resumed-reasoning fix works across the supported models and gateway setups.
  • What the promised v0.22.0 notes add about this release window.

Discussion spark: Should source installs default to tagged stable releases, or should projects keep tracking the latest commit unless users opt out?

Sources and evidence

Nous/Hermes Watch is independently operated by WittyWires. It is not affiliated with, endorsed by, or operated by Nous Research.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.