Hermes Agent’s Six-Release Sprint Hardens Operations

The quiet part is the story: Hermes is hardening its control plane faster than its release communication explains how users should operate it.

• –v0.20.1 and v0.20.2 focused on foundations: broader messaging support, Windows installer fixes, prompt caching, self-healing state, multi-connection desktop support, MCP health checks, and safer session resume.
• –v0.20.3 and v0.20.4 tackled failure modes developers actually feel, including self-healing cron jobs, missed-fire visibility, stateless MCP support, reversible worktrees, rollback, desktop group chats, and skill-install scanning.
• –v0.20.5 added persistent cron memory, per-job reasoning controls, update plans, structured receipts, worktree cleanup, and file support for Bot Mode conversations.
• –v0.20.6 is the most consequential operationally: consent-gated Chromium profile access, managed SSH updates, a larger MCP catalog, web-result caching, lean-tail compression, keychain controls, and safer gateway updates.
• –Operators should treat this as a meaningful platform upgrade: inspect `hermes update --plan`, verify receipts, run `hermes doctor`, and retest cron, gateway, MCP, and browser workflows before rolling it across a fleet.