v0.21.2 (v2026.9.11) — The state.db Patch Release
Released: September 11, 2026 Theme: Fixing the state.db problems some installs hit after v0.21.0
state.db is the database where Hermes stores conversation history. v0.21.0 rewrote its connection handling, and some installs became fragile: locks cancelled each other, healthy databases were reported as corrupt, and one bad row broke sessions list. If you hit these after v0.21.0, upgrade to this version or later.
Highlights
- No more second writers: several code paths opened a second writer on a database the gateway was using. They are gone.
- Healthy databases stop getting stuck: several cases that made a good database report errors are fixed.
- A damaged full-text index no longer ends your turn: search degrades, the index rebuilds later, and the transcript itself is untouched.
- One bad row no longer breaks the whole list: In
sessions list, export and insights, the bad row shows as?and a warning is logged. - Sessions never read another profile’s database.
- Opening the database is faster: it no longer takes the write lock when nothing needs writing. Starting Hermes behind a busy gateway used to stall 4–20 seconds; now it takes about 0.01 seconds.
- Multi-profile isolation: secondary profiles no longer inherit the default profile’s allow-lists, credentials or secrets.
- Password-blind credential vault: the agent can sign in, pay and fill addresses from 1Password, Bitwarden or the local vault without ever seeing a secret.
- Plugin catalog and one Plugins page (desktop app).
- Telegram: with
bots_require_mentionon, bots must @-mention each other to reply, which stops bot-to-bot loops.
Official link
Need a hand? Contact support · Cannot sign in? Email us