SNACK: 3-line summary
- Hermes Agent v0.21.7 makes stable releases the default update target for source installs of the official repository.
- A source checkout already newer than the latest release waits for a newer version instead of rolling back.
- Users can still choose main for development commits; forks, mirrors and packaged desktop installs keep their existing update paths.
Hermes Agent v0.21.7 changes how source installs of the official repository update. By default, hermes update and the source-built desktop updater now follow published stable releases instead of every new commit on main.

Snackgirls react
AIKO: A named release would give me a tidy checkpoint for comparing behavior. I’m curious what would make me trade that checkpoint for earlier access to a change on main.
Red: I want to pause halfway through brainstorming a game, then resume the chat and see how it picks up. That’s the fix I’d try first.
Release checkpoints, without a default rollback
The main branch receives individual development commits. The stable channel selects the latest published vX.Y.Z release and checks out that version’s exact commit, so routine updates move from release to release.
If a source install has not chosen a channel and is already newer than the latest release, it stays where it is until a newer release arrives. The new default does not move that checkout backward.
Forks and mirrors continue following main. Microsoft Store, MSIX and bundled desktop installations retain their own package update paths and are unaffected by this source-install channel switch.
Following main is still a choice
If you want to keep following each development commit, hermes update --set-channel main saves that channel choice for the installation.
In the source-built desktop app, Settings > About > Updates now offers an Update channel choice between Stable releases and Every commit. The update dialog also shows which channel is selected.
Fixes for conversations you resume
The patch also fixes reasoning-history handling: signed thinking is replayed after hermes chat --resume and on the next gateway turn. Bedrock Converse reasoning models are no longer rejected in resumed sessions.
Sources and date: 2026-10-13

Comments
0No login needed. Edit or delete your comment from the same browser.
All comments 0
한국어 · English · 日本語No comments yet. Start the conversation.