Hermes Agent v0.21.2 is out with a concentrated repair campaign for database failures and cross-profile isolation. The crucial point is practical: anyone whose sessions broke after v0.21.0, or who runs several profiles through one gateway, has a substantive reason to upgrade.
Nous/Hermes Watch analysis
What happened
Nous Research released v0.21.2 on 11 September, four days after v0.21.1. Its official release notes say six pull requests addressed the roots of state.db failures introduced around the v0.21.0 connection rewrite, closing 44 reported issues.
The release also rolls up 947 non-merge commits and 312 merged pull requests from a window involving 140 contributors. That is a formidable amount of plumbing, but the valuable parts are unusually concrete: safer database access, stricter separation between profiles and fewer ways for agent infrastructure to trip over its own shoelaces.
Our top picks
- Competing writers are removed
Hosted rooms move to shared-state.db, the dashboard opens read-only first and unsafe checkpoints are refused. - Healthy databases recover properly
Transient I/O errors, deleted WAL entries and races during writes should no longer leave a working store permanently wedged. - Search damage stays contained
A broken full-text index now degrades and rebuilds later instead of taking the transcript store and conversation down with it. - Bad rows stop poisoning sessions
Invalid timestamps or marker JSON no longer crash listings, exports or insights; malformed entries are identified and skipped safely. - Profiles keep their own secrets
The project says fixes prevent credentials, allow-lists, vault secrets, media and transcripts from crossing profile boundaries. - Idle reads become genuinely quick
Opening state.db behind a busy gateway reportedly falls from a 4 to 20-second failure to about 0.01 seconds. - Credentials stay out of the agent's view
Hermes can use 1Password, Bitwarden or its local vault to sign in and fill details without exposing the underlying secret to the model.
Why it matters
Persistent state is what turns an agent from a clever single-use demo into something people can trust with ongoing work. If that state corrupts, stalls or bleeds across profiles, every shiny model integration becomes expensive decoration.
The isolation fixes deserve particular attention. Nous Research is reporting repaired failure modes in its own software, not evidence that outsiders exploited them, but multi-profile operators should still treat this as more than routine housekeeping.
Our read
Upgrade if v0.21.0 left state.db behaving strangely, and prioritise the release if one gateway serves several profiles. Back up the relevant data first, then verify that sessions, search, exports and profile-specific credentials behave correctly after migration. The release notes are extensive, but the verdict is pleasantly short: this patch fixes the foundations.
What to watch
- Whether users confirm that previously wedged or damaged databases recover cleanly.
- Any follow-up security advisory clarifying the cross-profile isolation failures.
- Regression reports from multi-profile gateways and Desktop installations.
- Whether the new plugin catalogue's admission and pinning controls withstand wider use.
Discussion spark: Which matters more for trusting a long-running agent: stronger state recovery or stricter separation between profiles?
Sources and evidence
- Hermes Agent v0.21.2 (v2026.9.11) (11 September 2026, 19:20 UTC)
Nous/Hermes Watch is independently operated by WittyWires. It is not affiliated with, endorsed by, or operated by Nous Research.