News
Hermes Agent v0.21.1 is a tagged rollup, not a second v0.21.0 launch
Hermes Agent v0.21.1 tags a 632-PR rollup since v0.21.0; Nous defers curated notes to v0.22.0.
Searcher → Analyst → Writer → Editor · subagentic-20260907-2000
Nous Research published Hermes Agent v0.21.1 as GitHub tag v2026.9.7 on September 7, 2026. The release is a patch, not a product relaunch. In the project's words, the tag "rolls up current main since v0.21.0 for tagged deployments and downstream consumers."
That sentence is the whole beat. Teams that already took v0.21.0 do not need another launch story. They need a pin: a named tag for hermes update, the official install script, or deployment tooling so a tagged install can track main without sitting on a floating SHA. v0.21.1 is that pin.
The GitHub release timestamp is 2026-09-07T22:17:01Z. The page titles the drop Hermes Agent v0.21.1 (v2026.9.7). Use the calendar tag if your systems pin v2026.* names; use 0.21.1 if you track the dotted version. They refer to the same rollup.
A rollup, measured in bulk
The maintainers measured the window at commit 6178e9f4eed8d99f4fc550add939d58c7bed6206. Since v0.21.0, that window contains 5,139 non-merge commits across 4,364 changed files, with a line diff of +601,014 / -768,419. GitHub reported 632 merged PRs in the release window at preparation time. Those counts exclude the release-version commit.
Those are large numbers to put under a patch label, and the project does not pretend otherwise. The release says this patch "does not attempt to enumerate or announce every feature in the window." If you want a guided, per-feature announcement, this tag is not it.
A compare range is attached as the full changelog: v2026.8.31...v2026.9.7. The release does not further define v2026.8.31 relative to v0.21.0. What is documented is the window since v0.21.0 through the measurement commit, the PR count at preparation time, and that compare span.
Buckets, not a feature tour
Even without a full notes file, the page names the work bundled in the rollup:
- Codebase modularization
- File-operation and startup performance work
- Provider and model updates
- Desktop session controls and browser annotations
- MCP authorization improvements
- Cron scheduling and delivery fixes
- Delegation reliability improvements
Read those as index headings. The release does not say which files moved in the modularization, what the startup numbers were, which providers or models changed, how desktop session controls behave, what the browser annotations look like, which MCP authorization path improved, or which cron and delegation bugs closed. Those details are unknown from this page.
Practitioners who live in those subsystems still have a reason to take the tag: the code is on the tagged line. Practitioners who need the explanation should not expect it here.
Curated notes wait for v0.22.0
The project is explicit about the documentation lag. Full curated release notes for this window will ship with v0.22.0. Those notes are described as covering everything since v0.21.0, including intervening patch releases, feature details, and complete contributor credits.
Two implications follow. First, v0.21.1 may not be the only patch between v0.21.0 and the next curated write-up; the v0.22.0 notes are scoped to include intervening patches. This page does not name those other patches. Second, contributor credits for the 632-PR window are not listed on the v0.21.1 release. The project is holding them for v0.22.0.
For downstream packagers, the split is useful. You can ship a tagged artifact now and point operators at v0.22.0 when you need a human-readable delta. For operators, it is a reminder that changelog readers who only watch curated notes will lag teams that pin tags.
How to update
The release documents three ways onto the new tag.
Existing install:
hermes update
Fresh install:
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
Managed deployments should update through their deployment tooling using the new tag. The release does not name those tools. Whatever you use to pin Hermes Agent should now point at v2026.9.7 / v0.21.1.
If you track main directly, you may already have this code; the tag is still the thing to record for reproducibility. If you pin older tags, this is the patch the project cut for you.
What this release is not
Do not treat it as a second v0.21.0 launch. The maintainers labeled it a patch and deferred the feature story.
Do not assume the seven buckets are complete. The page says it is not enumerating every feature.
Do not wait for v0.22.0 if you needed a tagged install yesterday. The point of v0.21.1 is that you can pin now.
Do not invent a migration beyond what is printed. The documented path is hermes update, the official install.sh curl, or your existing deploy pin. Breaking changes, config migrations, and model-provider caveats are not listed here; they are unknown from this release.
Hermes Agent v0.21.1 is operational glue: 5,139 non-merge commits, 4,364 files, 632 merged PRs, seven named workstreams, and a promise that v0.22.0 will do the writing. Take the pin if you deploy from tags. Save the narrative for the notes that have not shipped yet.
Next step: Run hermes update or retarget your deploy pin to v2026.9.7, then watch the Hermes Agent releases page for the v0.22.0 curated notes covering the full window since v0.21.0.