Hermes Agent v0.23.1 patch restores plugin catalog installs after size cap bug
The patch raises the plugin catalog size cap to 16 MiB after larger catalogs made installs silently fall back to an older bundled catalog.
Hermes Agent v0.23.1, a patch release dated November 9, 2026, restores plugin installs that had been silently using an older catalog since the project's plugin catalog site deployed that same day. The published plugin-catalog.json grew past the 2 MiB cap that clients accept. Clients rejected the live file and fell back to the catalog bundled with each release. The release raises that cap to 16 MiB. The patch also rolls up about 618 merged pull requests since v0.23.0 across the CLI and installers, the Microsoft Store app, Docker and Hermes Cloud.
The failure was quiet. The GitHub issue reporting it was opened on November 9 and closed on November 10, when the fix shipped. According to the issue, the live document was 2,109,306 bytes with 1,268 entries at the 10:18Z deploy, against a limit of 2,097,152 bytes. The document before that deploy was 2,090,135 bytes, just under the line. When the live fetch failed, the only trace was a debug log line reading "live catalog payload too large." fetch_live_catalog returned nothing, so get_live_catalog_entry answered from the in-tree copy. As a result, hermes plugins install <name> could not find plugins added after a user's last update, installed the pinned version from the release rather than the current one, and missed removals published after the checkout. The issue's author flagged the removed list as the part that matters most for safety.
The issue also suggests why the file kept growing. Description fields accounted for 1.20 MB of the 2.11 MB, capabilities for 0.19 MB and known_issues for 0.10 MB. The author estimated each new entry at about 1.7 KB on average. Pull request #151860 by 100yenadmin, which fixes the client, makes the same arithmetic argument for the new cap: 16 MiB leaves room for roughly 9,000 entries at that size. Maintainer Teknium later noted that the published document had reached 2,302,549 bytes and 1,376 entries. Trimming descriptions to 280 characters would only bring it to about 1.35 MB, and growth of about 108 entries in 3.5 hours would use up that headroom in roughly a day. That is why the maintainer chose a client-side change for the cap rather than a server-side trim.
The cap change only helps clients that update. The pull request says clients already installed keep the 2 MiB cap until they update, and the release notes say installs on v0.23.0 or older keep falling back until they do. Those installs need the site-side fix discussed in the issue: keeping the published document under 2 MiB. The pull request leaves the method to the maintainers, whether through summary-length descriptions, a second document or a build check, and it leaves the site build alone. Users update through hermes update or the installer one-liner for the CLI, through the Microsoft Store for that app, and by pulling nousresearch/hermes-agent:stable or :latest for Docker and Hermes Cloud. The desktop installer app gets no change in this release and updates with the next bundled release.
The release notes leave part of the window's work undocumented on purpose. They mention features such as Esc backtrack in the TUI and classic CLI, group chats on a gateway, saved gateway connections shared by Desktop and the Webapp, and a new plugin API. Full curated notes covering everything from v0.23.0 onward are promised with v0.24.0. The release measured 2,578 non-merge commits across 2,781 changed files, with 618 merged PRs and 409 closed issues.
What changed
Hermes Agent v0.23.1 raises the plugin catalog size cap from 2 MiB to 16 MiB, so clients stop falling back to the bundled catalog when plugin-catalog.json grows past 2 MiB.
Type: Outage · Takes effect: Monday, November 9, 2026 · Applies to: Hermes Agent v0.23.1, plugin-catalog.json, hermes plugins install
Why it matters
Teams that install agent plugins through the catalog may have received outdated versions without any error, and plugins removed from the catalog could still be present on machines that have not updated.
What you can do
Update Hermes Agent to v0.23.1 using hermes update, the installer, the Store app or the stable Docker image, and review plugins installed since November 9 against the current catalog.
Original source
- github.comRelease Hermes Agent v0.23.1 · NousResearch/hermes-agent · GitHub
- github.comfix(plugin-catalog): accept the published catalog past 2 MiB by 100yenadmin · Pull Request #151860 · NousResearch/hermes-agent · GitHub
- github.com[Bug]: the live plugin-catalog.json is now over the client's 2 MiB cap, so clients fall back to the in-tree catalog · Issue #151856 · NousResearch/hermes-agent
Where we saw it
Hermes Agent releases
AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works