Nous Research released Hermes Agent 0.23.1 with a correction to how clients accept the current plugin catalog. Its notes label the release November 9, 2026, while GitHub displays publication on November 10. We preserve both records rather than deriving a separate, nonexistent product launch from the difference.

According to the maintainers, the live catalog exceeded the size accepted by older clients. They fell back to a bundled copy that could contain older versions and omit newer entries. The correction raises the limit from 2 to 16 MiB. This changes catalog retrieval; it is not an announced improvement in the intelligence of the underlying model.

A catalog is different from a plugin

The official documentation describes plugins as a way to add tools, hooks and integrations without modifying core code. A catalog helps locate and select a package. Installing that package is a subsequent step, while activation and permissions are other parts of the workflow.

This leads to an important editorial distinction. Successfully loading a list does not establish that an installed component has been updated. A familiar plugin name also does not establish which version is executing a tool. An operator needs to distinguish what was found, what was installed and what is active in the particular session.

The linked merged pull request describes checks for accepting a document above the old threshold and refusing a document above the new limit. These are inspectable code changes and developer-reported test results. SIExpo has not executed the test suite and does not present them as its own measurements.

Why fallback can conceal a problem

A bundled copy has practical value when a network source is unavailable: some work can continue. If the use of that older state is invisible, however, an operator may mistake the displayed list for the current one. The problem then concerns both availability and the accuracy of the status presented to the user.

Our example is a team expecting a newly released tool version. If its client sees only an older catalog, repeating the same command does not guarantee a new result. Establishing which source was used and why comes first. This is a general diagnostic approach, not an instruction to run unverified commands in production.

A useful log would distinguish a successful network check, a cached response and the bundled fallback. It would then show the selected version. One generic completion indicator does not answer those questions. This is our criterion for evaluating such systems, not an additional feature we attribute to Hermes.

Updating has a specific scope

The release notes distinguish distribution channels. Microsoft Store updates through the store, while CLI and container variants have their own routes. For Desktop installed through a separate installer, the change arrives with a subsequent bundled release. A release number on GitHub therefore does not mean every already-open client has changed.

For a controlled review, we would record the current version, distribution channel and catalog-check outcome before and after updating. We would separately verify whether the expected plugin is installed and enabled. None of this requires revealing credentials or broadening the agent's access.

That separation also helps determine whether a remaining failure belongs to discovery, installation or execution. Treating those as different stages avoids repeatedly changing a working component while overlooking a stale dependency. It is a proposed troubleshooting method, not a claim that SIExpo has diagnosed a user's live Hermes environment.

This is a concrete reliability correction in an open agent ecosystem. It illustrates how a limit in a supporting service can change the tools actually available even while conversation with the model appears normal. For deployment teams, visibility into those dependencies matters more than a vague promise of another smarter agent.

Sources: Nous Research — Hermes Agent 0.23.1 release notes, Hermes — merged catalog size-limit fix, Hermes — plugin architecture and security. The cover is a conceptual AI editorial illustration, not a documentary photograph.

Editorial verification: 2026-11-10T17:08:25.417687+00:00.