SIAgentNews.com
← All news

Hermes Agent v0.23.3 rolls up about 370 merged changes into one stable patch

Nous Research's open-source agent has a new patch release with caching, setup and storage changes, but the full notes won't arrive until v0.24.0.

· First reported by github.com

370merged pull requests rolled into this patch

The short version

  • v0.23.3 is dated November 19, 2026 and bundles 370 merged PRs since v0.23.2.
  • The window spans 1,657 non-merge commits and 3,948 changed files, with 60 closed issues.
  • Listed items include prompt-cache handling, a one-question first-run setup and a storage-layer split.
  • Full curated notes will ship with v0.24.0, covering everything from v0.23.0 onward.
  • Update paths differ: Store app, CLI, Docker and Hermes Cloud update, while the desktop installer does not.

Why it matters

If you run Hermes Agent, this is a large amount of change inside a small version number, so the number alone says little about the risk of upgrading. The release also shows how fast an open-source agent project moves and how much you have to read to keep up. Pin your working version and test the new one on a copy before you switch.

A small version number, a big pile of work

Hermes Agent, the open-source agent from Nous Research, has a new tagged release: v0.23.3, dated November 19, 2026. As github.com reported on its release page, it is a patch release. It gathers roughly 370 pull requests (proposed code changes that were accepted and merged) made since v0.23.2.

The size of that window is unusual for a patch. The release page counts 1,657 non-merge commits (individual saved changes), 3,948 changed files, and 60 closed issues. The line counts are +222,379 and −96,154, meaning a lot of code was added and a lot was removed.

The point of the tag is to give several kinds of users a stable version to land on: people on the GitHub release (the command-line tool and its installers), the Microsoft Store app, Docker users, and Hermes Cloud.

What the maintainers say changed

The page says it deliberately leaves many changes undocumented for now, and it lists several anyway. Taken together they hint at where the project is putting its effort.

  • Prompt caching. A prompt cache is a temporary store a model provider keeps so repeated context doesn't have to be reprocessed. The release adds a controller that manages this over time. It keeps the cache warm during long tool runs and compacts idle chats before the one-hour cache expires. Nous Portal gets the full one-hour lifecycle, and the cache_ttl setting now defaults to auto.
  • Compaction and pruning. Compaction shrinks a long conversation so it fits in the model's working memory. It now archives the tool results it drops, and a proactive prune of tool results is on by default.
  • Easier first run. The command-line setup now asks one question, and the free tier is included.
  • New models. GPT-6.2 Astra and Sol, plus a Pro version, are listed on OpenRouter and Nous Portal.
  • Interface and packaging. A "Waiting on teammates" strip appears above the Bot Chat composers. The Linux AppImage runs its agent payload from a stable copy made for each build.
  • Storage. The storage layer now sits behind a persistence interface, with SQLite (a small file-based database) as its backend.
  • Security and plugins. Dependencies oauthlib, opentelemetry and tornado got security bumps, and many new entries were added to the plugin catalog.

What these changes mean in practice

Several items concern the cost of long agent sessions. An agent that calls tools for a long time builds up a lot of text, and managing that text well matters for both speed and spend. The release page does not say how much faster or cheaper any of this makes things, so treat those effects as unmeasured.

The storage change is mostly invisible to users. Putting storage behind an interface usually makes it easier to swap in a different database later. That is an inference on our part, and the release page does not state a plan.

One default is worth noting. The proactive tool-result prune is on by default, so your agent may behave differently on long tasks without you changing a setting. If you rely on exact tool output staying in context, watch for this. Compaction now archives what it drops, which is the safety net here.

How to update, and who gets left out

The update route depends on how you installed it:

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

The desktop-installer exception is easy to miss. If you installed that way, you won't see these changes yet, and that's by design.

The catch: the notes are deferred

The maintainers say the full curated notes will come with v0.24.0. That release will document everything from v0.23.0 onward, with highlights, feature areas and complete contributor credits, and they say nothing in this window is skipped. So the information exists, but it isn't on this page yet.

That leaves a gap for anyone deciding whether to upgrade today. The release lists changes, but it does not explain behavior, settings or migration steps. The sensible habit is the usual one: keep your current version, update a copy, and rerun one real task before relying on the new build. With roughly 370 merged changes, a patch number is not a promise that nothing will feel different.

What to watch

  • What the v0.24.0 notes say about the prompt-cache controller and the default tool-result prune.
  • Whether the desktop installer gets its own update soon, since it skips this release.
  • Whether the storage-layer split leads to other database options beyond SQLite.

Try it

Before updating, note your current Hermes version, then update a separate copy and rerun one real task. Compare results and check whether long sessions behave differently with the new default prune.

Sources and links

First reported by github.com. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.

Liked it? Say why

Add a line for other readers.

No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.

More AI news