Release guide · August 4, 2026
Hermes Agent v0.20.0: what changed and what to test
A direct guide to Hermes v0.20.0 voice, grounded citations, desktop artifacts, signed webhooks, A2A, and safe upgrade checks.

v0.20.0 is useful for voice, research, desktop artifacts, and external automation. Upgrade a non-production profile first, verify the runtime selected by the official installer, and treat every performance figure as a maintainer measurement until you reproduce it.
The best place to start with Herald is a research brief you can actually hand to someone: sources attached, revisions visible, and a file you can inspect. I would try that before connecting another agent or enabling an always-listening microphone.
Hermes Agent v0.20.0, released on August 3, 2026 as v2026.8.3, adds streaming voice, grounded citations, versioned desktop artifacts, signed webhooks, A2A communication, and long-session reliability work. Hermes is still an agent harness, not a new foundation model.
Checked November 16, 2026: this is a historical release guide. The feature descriptions below come from the linked release and implementation notes. The exercise is a proposed acceptance test, not a report of Superbash running Hermes v0.20.0.
Decide what to test first
| Your workflow | Test first | Pass condition |
|---|---|---|
| Voice | Playback, interruption, microphone permission, and reply routing | Hermes stops promptly and preserves the correction |
| Research | Citation ledger and source support | Every material claim opens to a supporting source |
| Desktop output | Preview, source, versioning, and download | All views contain the same reviewed result |
| Webhooks | Signature validation, retry, and deduplication | Invalid signatures fail and duplicate delivery IDs do not repeat work |
| Agent-to-agent work | Authentication, turn limits, and credential filtering | The target receives a bounded task without exposed secrets |
Voice supports interruption
v0.20.0 can synthesize sentence-sized chunks while the model is still generating the next part. Barge-in stops playback when the user begins speaking, keeps the opening of the interruption, transcribes it, and uses it as the next turn.
Wake-word listening is optional. The default phrase is “Hey Hermes,” and enabled profiles can use separate phrases. The listener can run on-device while waiting, but the complete voice path may still use external speech, model, or messaging providers. Review each provider’s permissions and retention policy.

Grounded citations keep a source ledger
The grounded-citations skill assigns source IDs during retrieval, stores them in a ledger, renders the source list, and checks whether citations still map to the right URLs. This catches missing sources, broken IDs, and mismatched references.
It does not prove a claim is true. A real source can be irrelevant or wrong. Open each source and check that it supports the sentence that cites it.

Desktop artifacts make large output inspectable
Hermes Desktop can promote substantial HTML, SVG, and code into an artifact card. The side panel supports version history, preview and source views, copy, download, and opening HTML in a browser.
Generated HTML runs in a sandboxed iframe without same-origin access, and SVG is sanitized. Inspect the source before distributing or opening sensitive output.

Try it: turn a cited brief into a reviewable artifact
Use a disposable research profile with public-source retrieval enabled. In Hermes Desktop, ask for a short brief about one question you already need answered. Here is a suggested prompt, not a tested transcript:
Use grounded-citations to compare the installation routes described in
Hermes's official v2026.8.3 release notes and tagged installation guide.
Register sources as you retrieve them. Separate agreement, disagreement,
and anything you cannot verify. Do not install or update anything.
First show the brief with citations and its rendered source list.
Then present it as a self-contained HTML document, with no scripts or
external assets, keeping the citations and source links intact.
Open each source and check one disputed detail before asking for a revision. For example, the Node requirement discussed below is a better test than asking the model to repeat the release highlights.
The original artifact implementation detects full HTML documents; ordinary Markdown and small snippets do not become artifact cards. If you only get prose, ask for a complete HTML document in an HTML code fence. Do not pad it with irrelevant content just to trigger a card.
Once the card appears, ask Hermes to correct one sentence and regenerate the document with the same title. The implementation groups regenerated content by kind and title within a session. Check both versions, compare preview with source, and download the corrected version. Changing the title can create a separate artifact instead of another version.
Keep the result only if the corrected sentence survives the download, its citation still supports it, and you can identify the earlier version. If the citation is unsupported, remove or qualify the claim and regenerate. If version history fails, save the two files separately and record that the artifact test did not pass. A nice preview alone is not enough to call this workflow ready.
Webhooks and A2A connect external systems
Signed outbound webhooks can send session, turn, and tool events to an HTTP endpoint. The receiver should verify the HMAC-SHA256 signature over the raw body, reject stale events, and deduplicate delivery IDs. Do not accept an event only because its JSON has the expected shape.
The webhook implementation uses a bounded queue: connection errors and server errors get one retry, client errors do not, and a full queue drops events with a warning. A signed event proves neither durable delivery nor completion of the receiving job. I would use this first for a dashboard notification. If it triggers important work, keep a receiver-side record keyed by delivery_id and reconcile missing events separately.
For a disposable receiver test, send one valid event, replay its delivery ID, and send a modified body with the original signature. Expect one accepted job, no duplicate job, and rejection of the tampered body. Those are acceptance criteria to implement and verify, not guarantees supplied by the sender.
The bundled A2A v1.0 plugin can discover and call compatible agents or expose Hermes as an A2A agent. Default controls include localhost-only access without a token, bearer-token support, prompt-injection filtering, credential redaction, callback checks, audit logs, and turn caps. Use authentication and network controls before exposing it beyond localhost.
Small command-line changes
| Change | Use |
|---|---|
!command | Run a shell command through the normal approval gate without spending a model turn |
/init | Generate or update repository instructions |
/diff | Inspect changed files |
/context | See what occupies the context window |
/focus | Reduce noisy output while keeping a recovery path |
| Mid-turn redirection | Correct the active task without restarting the whole conversation |
The default tool-iteration limit also increased from 90 to 500. Add a step limit, cost limit, and explicit stop condition before allowing long unattended work.
Treat speed figures as test targets
Nous reports faster cold starts, updates, prompt caching, and desktop rendering. These are maintainer measurements. Provider latency, hardware, profile size, tools, network, and accumulated state can change the result.
Measure the workflow you use: cold start, time to first response, successful tool completion, total elapsed time, and recovery after one controlled failure.
Upgrade safely
The release notes say Node 26 is required and retire Homebrew and PyPI wheel distribution in favor of the supported installer, Docker, or Nix. The tagged installation page still contains older Node wording. Do not choose a runtime manually from one sentence.
For an update today, follow the current updating guide, checked November 16, 2026. It distinguishes managed source installs (hermes update), packaged desktop apps (their app/store update route), Docker (replace the image while retaining the data mount), and Nix (update and rebuild). The source updater follows its configured channel; running it does not specifically install v0.20.0.
- Back up the Hermes configuration and note the current version.
- Update through the supported route detected for your installation.
- Run
hermes doctor, save its diagnostic output privately, and record the installed version and runtime. Redact credentials before sharing diagnostics. - Test one ordinary task in a non-production profile.
- Verify model routing, approvals, message delivery, plugins, and webhooks you rely on.
- Reconnect production messaging only after the test passes.
Who should upgrade first
Upgrade a test profile if you use Hermes Desktop artifacts, voice, cited research, signed event delivery, or long sessions that often lose context. Delay a critical shared gateway until you have tested custom plugins, older runtime assumptions, message routing, and rollback.
Sources
Official sources checked November 16, 2026. Release-era implementation notes describe the original behavior; the current updating guide is linked separately for present-day installation decisions.
Put this to work
Choose one capability and trace the complete path from input to reviewed result.
Try
Build a cited research brief and save it as a versioned desktop artifact.
Prove it worked
Open every citation, inspect the artifact history, and document the failure and rollback path.
Where it can pay
Reviewed research and operations workflows become useful services when approval points and maintenance are explicit.
Keep in view
- Streaming voice can start before the full response is ready and stop when the user interrupts.
- Grounded citations use a source ledger, while desktop artifacts add versioned previews for substantial output.
- Signed webhooks and A2A connect Hermes to external systems and agents, but still require authentication and bounded permissions.