Hermes Agent v0.22.7 bundles about 174 merged changes into one stable patch

A patch tag with a lot inside

Hermes Agent is an open agent framework from Nous Research. An agent, in this context, is software that uses an AI model to carry out multi-step tasks rather than just answer a question. As github.com reported on its release page, version v0.22.7 is a patch release dated November 3, 2026.

A patch release usually suggests a small fix. This one is not small. The page says it gathers about 174 merged pull requests (proposed code changes that were approved and added) made since v0.22.6. It packages them as one stable version for several delivery channels: the GitHub release with the command-line tool and installers, the Microsoft Store app, Docker, and Hermes Cloud.

The size of the window

The listing measures the work at a specific commit, b200f5bc60e. Between v0.22.6 and this tag it counts 581 non-merge commits (individual saved changes, not counting the bookkeeping entries that join branches together). Those touched 554 files, adding 24,012 lines and removing 3,144. It also records 29 closed issues, meaning reported problems or requests that were resolved.

Those figures describe volume, not quality. A large diff can hold careful fixes, new features, or both. The numbers tell you the jump from v0.22.6 is bigger than the version number implies, and nothing more.

What the page hints at

The page does not name one headline change. It does, however, list a group of items that landed in the same window and that it deliberately leaves undocumented for now. Most concern group chats in the desktop app:

• An optional way for one participant to take the lead in a group conversation, shown with a badge on the room header.
• Scheduled jobs that can post into group chats, plus a stated purpose and shared notes for each room.
• A redesigned room layout in a single column that shows each member's live status.
• Kanban boards (task boards with columns) that can be pinned as quick-switch tabs.

Other items are smaller. The page mentions diagram labels written in TeX (a math typesetting language) and Mermaid diagrams (charts drawn from plain text), both rendered through a component called Pele. The desktop updater now shows the output of a failed update along with a way to report the problem. Web Access names the step it is on and runs a clock.

On the integration side, Telegram on Team Gateway is set up by linking an account to a shared bot. There is an optional Slack setting called thread_followup_silence, aimed at thread replies not addressed to the agent. A switch called Daybreak relates to ChatGPT subscription models that appear in the catalog. The page also mentions a batch of new plugin-catalog entries.

Treat this as a pointer, not a changelog. The page does not describe how any of these behave, so details are unconfirmed until the full notes appear.

How to update, by install type

The page is specific about how each version of the product receives the release:

• Microsoft Store app: updates through the Store.
• Desktop app from the installer (.exe or .dmg): no change in this release. It picks up changes with the next bundled release.
• Command line: run hermes update, or run the installer one-line command again.
• Docker and Hermes Cloud: use the image nousresearch/hermes-agent with the stable tag (or latest).

The desktop point matters. Someone who installed the desktop app from a file will not see v0.22.7 changes yet, even though the group-chat features above are described as part of this window.

What comes next

The maintainers say full curated notes will ship with v0.23.0. Those notes are meant to cover everything from v0.22.0 onward, including highlights, feature areas and complete contributor credits. The page states that nothing in this window is skipped, so the missing detail is a matter of timing, not omission.

For a cautious user, that suggests a simple routine. Note your current version before upgrading so you can go back. If you use Docker, record which tag you were running. Try the new version on a workflow where a mistake costs little, and read the v0.23.0 notes once they exist to learn which of these changes affect you.