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.3 rolls up 370 pull requests

Written November 20, 2026

Hermes Agent 0.23.3 is a rollup of about 370 pull requests since 0.23.2, with a prompt-cache lifecycle controller and compaction that archives tool results.

Hermes Agent v0.23.3, dated November 19, 2026, calls itself a patch release. The patch rolls up the roughly 370 pull requests merged since v0.23.2 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. The previous release, Hermes Agent 0.23.2, used the same rollup shape at a much larger scale. This one is smaller, and it carries the same catch: the full story of what changed is deliberately deferred.

How big the rollup actually is

The release gives its own measurements, taken at commit caafe5389ae. The window since v0.23.2 contains 1,657 non-merge commits across 3,948 changed files, with 222,379 lines added and 96,154 removed, alongside 370 merged pull requests and 60 closed issues. That is far too much change to judge from a single feature, and the release does not try to summarize it. Instead, it names a set of behaviors that changed in the window, gives the update path for each install channel, and leaves the explanation for later.

The deferral is explicit. Full curated release notes for this window ship with v0.24.0, which will document everything from v0.23.0 onward — highlights, feature areas, and complete contributor credits. The release is clear that nothing in this window is skipped there. It is postponed, not dropped. For a user deciding whether to update now, that means the honest basis for the decision is the scale above, the named items below, and whether the update path for your channel is routine.

Named in the release, documented later

The release names the following changes and then says, in its own words, that they are undocumented here on purpose. Treat the list as signposts: the release confirms each item is in this window, and the writing about it arrives with v0.24.0.

Two items carry practical weight even without documentation. The prompt-cache lifecycle controller ties together warming, idle-chat compaction, and a cache setting that now defaults to auto — anyone whose work involves long tool runs or chats left idle will feel that behavior before they read about it. And compaction that archives the tool results it drops, paired with a proactive prune that is now on by default, changes what a long session keeps and what it sets aside. Both are reasons to run one familiar task after updating, rather than assuming a patch release changes nothing you use.

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.

Verdict

Take the update through your normal channel, knowing the feature story is deliberately unfinished. Because 0.23.3 is a rollup, the useful check after updating is not the changelog — the curated version does not exist yet — it is the named behavior you rely on: the prompt-cache lifecycle, the compaction that archives dropped tool results, or the first-run setup. Run that one thing once before trusting the new build with real work, and expect the fuller account when v0.24.0 ships.

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Hermes Agent 0.23.2 rolls up 1,989 pull requests