Hermes Agent v0.20.6 rolls up 525 PRs with real-profile browsing

Nous Research has pinned Hermes Agent v0.20.6 as GitHub tag v2026.8.27, published August 27, 2026 at 12:06:53 UTC. It is a patch release, not a minor-version story: the notes say the tag rolls up the roughly 525 pull requests merged since v0.20.5 into a stable pin for Docker images, hosted deployments, and fresh installs.

If you are still pulling the August 21 line — v0.20.5, tagged v2026.8.19 — this is the new downstream target. The project is also clear about what the tag is not. Full curated release notes for the window will ship with v0.21.0, covering everything from v0.20.0 onward: highlights, feature areas, and complete contributor credits. Nothing in this window is skipped. It is just not documented as a long-form changelog yet.

An independent recap on hermes-agent-lab.com restates the same patch: about 525 PRs and 1,313 commits since v0.20.5, with the same headline features.

How large the window actually is

GitHub's release prose puts the delta since v0.20.5 at ~1,313 commits across ~1,557 files (+177,113 / −21,682) and ~525 merged PRs. That is a lot of surface area for a patch tag, which is why the notes frame v0.20.6 as a consumption pin rather than a narrative release.

The compare range for the window is v2026.8.19...v2026.8.27.

The change operators will feel first is consent-gated real-profile browsing. Hermes can use the operator's default Chromium profile for local browsing, with a Windows close-with-approval flow. The lab recap puts it this way: it "lets the agent browse as you with your real logins."

That is not a throwaway browsing session. Once you allow it, the agent is using the same Chromium profile — and the real logins on it — that you already run locally. Operators who keep Hermes on the workstation that holds their daily browser profile should treat the consent gate as a real policy choice.

On the desktop, the Browser also gets its own OS window, plus a managed SSH remote-update engine and a fleet profile rail. Browsing is a first-class window, and remote-update plumbing landed in the same patch.

Fifty-plus live MCP servers, and TTL caches for web tools

The remote MCP catalog expands to 50+ live-verified vendor-hosted servers. GitHub names Cloudflare, Grafana Cloud, Better Stack, and Railway among them. The lab recap matches the "past 50 live-verified vendor servers" count. This is catalog growth — more vendor-hosted MCP endpoints checked live — not a new MCP protocol in this tag.

In the same window, TTL result caching lands for web_search and web_extract. Lean-tail compression becomes the default. tool_search gains multi-query searches with stemming. Those three are the fetch-and-discoverability cluster: cache web results with a TTL, compress the tail by default, and let tool search issue more than one query with stemming.

Keychain secrets, safer updates, quieter ops

Stored secrets can opt into OS-keychain encryption. GitHub's practical note: no more per-launch macOS Keychain prompts. Encryption is opt-in; the payoff is that secrets can sit behind the operating system's keychain instead of prompting on every launch on macOS.

Updaters pause gateways over the control socket instead of tree-killing them. Image- and package-managed installs refuse unsafe in-place updates (#91277 Phase 3) — relevant if you consume Hermes as an image or a package rather than a git checkout. Cron picks up durable-incident acks and clearer code-skew failures. The same patch list also includes Slack link-unfurl controls, shared Docker container identities, and pluggable terminal environment backends.

Taken together, the ops cluster is about not yanking gateways down, not letting image and package installs mutate themselves unsafely, and making cron failures and Docker identity sharing less ambiguous.

Models in the pickers

New models across the pickers: GLM-5.3-Flash, MiniMax M3 free, and MiniMax H3 Max video. The release notes do not add context-window, pricing, or provider-mapping detail beyond those picker labels.

Upgrade path

From an existing install, the documented path is still hermes update. Fresh installs are directed to the project's install script on the GitHub release. Downstream consumers who pin Docker tags or hosted images need v0.20.6 / v2026.8.27, not the August 21 v0.20.5 tag.

If you need the browsing, MCP catalog, TTL cache, or keychain behavior, take this tag now. If you were waiting for a curated narrative, wait for v0.21.0 — but do not confuse that wait with nothing having shipped.

Next step: Open the GitHub release for v2026.8.27, then run hermes update on existing installs — or retarget Docker and hosted pins to v0.20.6 — before you enable consent-gated Chromium-profile browsing or OS-keychain secret encryption.