Hermes Agent Just Got More Reliable: The Care Behind a Simple Patch
Hermes v0.22.7 update: what changed in this release, explained in plain language.
Version Info
| Item | Content |
|---|---|
| Version | v0.22.7 |
| Release Date | November 3, 2026 |
| Release Type | Patch Release |
| One-liner | Consolidates roughly 174 improvements accumulated since v0.22.6 into a single stable release, covering the CLI, installers, the Microsoft Store app, Docker, and Hermes Cloud. |
Plain-English Breakdown
This update doesn’t come with big, flashy new features—it’s more like a thorough round of fixes after a full checkup. The team bundled a bunch of changes that had been merged in piecemeal over time into one stable release, so users across all channels get the same reliable code. Here are a few of the points ordinary users will notice most.
Desktop chat no longer gets its wires crossed
If you’ve ever sent messages in a row in the desktop app, hit stop partway through, then fired off a new command, you might have occasionally seen tool-call records land in the wrong turn—last round’s tool results showing up out of nowhere in the new round, or the same tool record drawn twice. This release fixes a batch of these “turn boundary” issues: queued prompts now correctly mark their own starting position, late-arriving tool events are matched to “the same call,” and calls that have already finished only display once even if they’re delivered again. In plain terms: the chat log’s ledger is kept more accurately now—it won’t charge the previous entry to the next one.
Queued messages get “their own identity”
Previously, if you sent several messages in a row, the system might lump them into a single turn. Now each queued prompt is treated as an independent turn with its own starting point and boundaries. For users, the most direct feeling is: every message you send is taken seriously—no more quiet merging or misplacement.
Smarter deduplication of tool calls
When an AI agent does its work, it calls various “tools” (search, read/write files, etc.). Network hiccups or UI redraws can cause the same tool event to be delivered more than once. This change lets the system judge whether it’s a late old message or a genuinely new call based on “parameters + the turn it belongs to,” avoiding duplicate rendering. It’s like when a package gets scanned twice at the warehouse—they don’t ship it to you twice.
Tests kept pace too
Beyond bug fixes, this release adds tests for “stop” and “optimistic send” scenarios, making sure edge cases around tool ID reuse are covered. For ordinary users, this means these fixes weren’t just made on a whim—they’re backed by tests.
Summary
v0.22.7 is a classic “stability above all” patch release: no dazzling new features, but it tackles a batch of nagging little problems all at once—messed-up desktop chat logs, fuzzy boundaries for queued messages, and duplicate tool event displays. For anyone using Hermes Agent day to day, the most direct payoff is more coherent conversations, more trustworthy records, and fewer baffling duplicates and misplacements. The team also says the full curated notes for this window will ship alongside v0.23.0—worth looking forward to.
📎 Official release notes: https://github.com/NousResearch/hermes-agent/releases