Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Hermes Agent 0.23.2 rolls up 1,989 pull requests

Written November 17, 2026

Hermes Agent 0.23.2 is a patch rollup of about 1,989 merged PRs. Full notes wait for 0.24.0, but the release names what changed underneath.

Hermes Agent v0.23.2, released on November 16, 2026, calls itself a patch release, and the patch is enormous. The tag rolls up the roughly 1,989 pull requests merged since v0.23.1 into a stable release for the GitHub release — the command-line tool and its installers — the Microsoft Store app, Docker, and Hermes Cloud. If you run Hermes in any of those forms, this is the current stable build. What it is not is a release you can read in the usual way: the release says plainly that the full curated notes for this window ship later, with v0.24.0.

How big the rollup actually is

The release gives its own measurements, taken at the release commit. The window since v0.23.1 contains 7,918 non-merge commits across 5,211 changed files, with 239,733 lines added and 22,788 removed, alongside those roughly 1,989 merged pull requests and 940 closed issues. A change list that size would be a book, not a release page, so the project is holding the writing for the next minor release. The v0.24.0 notes will document everything from v0.23.0 onward — highlights, feature areas, and complete contributor credits — and the release is explicit that nothing in this window is skipped. It is postponed, not dropped.

That leaves a problem for anyone deciding whether to update now. You cannot scan a feature list and judge the release by the one change you care about. The release page instead gives you changes it names without explaining, fixes it does stand behind, and the update path for your channel.

Named in the release, documented later

The release names a set of changes and then says, in its own words, that they are undocumented there on purpose. Treat the list as signposts, not explanations: the release confirms each item changed in this window, and that the writing about it arrives with v0.24.0.

Two deserve a pause even without documentation. A subagent that survives a gateway restart changes what a long delegation can promise, because a crash stops being the end of the work. And an update command that stops gateways at once, rather than draining them, changes what hermes update --force does to work in flight.

The fixes the release does stand behind

Separate from the rollup, the release lists seven fixes from its release candidate. These are the concrete changes in 0.23.2, and most are about desktop and chat surfaces dropping, duplicating, or scrambling work.

If you hit any of those — the stuck Stop button and the duplicated reply after a crash are the likeliest to have cost someone an afternoon — 0.23.2 closes them now. You do not need to wait for v0.24.0.

How your install receives it

Updating differs by channel, and one channel gets nothing this time. The Microsoft Store app updates through the Store. The desktop app installed from the installer has no change in this release; it updates with the next bundled release. On the command line, run hermes update, or re-run the installer one-liner. Docker and Hermes Cloud take the nousresearch/hermes-agent:stable image tag, or :latest. The previous release, Hermes 0.23.1: the plugin catalog cap fix, was a single-issue patch. This one is a rollup of everything since.

Verdict

Take the update for the seven candidate fixes if any bite you, knowing the feature story is deliberately unfinished. Because 0.23.2 is a rollup, the useful check after updating is not the changelog — there barely is one — it is the named behaviour you use: a durable subagent, a cron option, a plugin API. Run that one thing once before trusting the new build with real work.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Hermes 0.23.1: the plugin catalog cap fix