Source: raw/reddit-1v1vey8.md (r/hermesagent, u/FilterJoe, posted 2026-07-20) cross-checked against the official GitHub release notes (github.com/NousResearch/hermes-agent/releases/tag/v2026.7.20) fetched 2026-07-20. The release, the “Quicksilver” name, the TTFT/latency claims, the commit/contributor tallies, and the feature list are all confirmed by the official notes. Update via hermes update.

Hermes Agent v0.19.0 (“The Quicksilver Release”, 2026-07-20) is a speed release: the team spent the window making the messenger god move like his name. First-turn time-to-first-token dropped ~80% on every platform, reasoning models stream their thinking live by default, the desktop app got a ~20-PR performance overhaul, and the TUI now renders markdown incrementally. Around that speed spine the release adds terminal-native subscription management, password-manager credential integration, smart approvals on by default, live subagent monitoring, and a durable delivery ledger so a finished response survives a gateway crash. Where v0.18 “The Judgment Release” turned inward to triage the P0/P1 backlog and promote Mixture-of-Agents to a first-class provider, v0.19 turns to latency and reliability — “Quicksilver” is the old name for mercury, the metal named for the same fleet-footed messenger god Hermes is.^[inferred: name interpretation not stated in the source] The release also rolls up everything from the v0.18.1 and v0.18.2 infrastructure patch tags (full changelog range v2026.7.1…v2026.7.20).

Key Takeaways

  • First-turn TTFT down ~80% on every platform. The cold-start “Initializing agent…” delay that used to eat ~4.3 seconds is now ~0.9s. Reasoning models stream their thinking live by default, and per-token response-box painting replaces the old line-based rendering.
  • Desktop app ~20-PR speed overhaul. 14x less splitter CPU via incremental block lexing for streaming markdown, virtualized review-pane diffs that eliminate full-Shiki freezing, no more layout thrashing on session switch, and eliminated sidebar/tool-row re-renders during streaming.
  • TUI renders markdown incrementally — per block rather than re-painting the whole buffer.
  • Manage your Nous subscription from the terminal. New /subscription command (view plans, remaining allowance, upgrade-cost preview) and /topup for adding credits, with scheduled-change banners and undo; the desktop app gets a matching billing settings tab.
  • Bitwarden + 1Password integration. A pluggable SecretSource interface supports both managers (multiple vaults simultaneously with deterministic precedence), consolidating eleven competing community PRs into one interface.
  • Smart approvals judge flagged commands by default. An LLM independently assesses flagged commands rather than pattern-matching against prior approvals; user-defined deny rules block commands even in yolo mode, and /deny <reason> feeds the refusal back to the agent to course-correct.
  • Watch subagents work live. delegate_task now returns live transcript files you can tail -f; background delegations are durable and survive restarts, with an ownership-checked ledger preventing result loss.
  • Durable delivery ledger. A finished response that used to vanish if the gateway died between generating and confirming it is now recorded in the state.db ledger and redelivered on next boot across Telegram, Discord, Slack, and other channels.
  • Rolls up v0.18.1 + v0.18.2. The two infrastructure patch tags between v0.18.0 and this release are fully documented in these notes.

Release by the numbers

Since v0.18.0 (per the official notes):

  • ~2,245 commits · ~1,065 merged PRs · ~2,465 files changed
  • ~300,000 insertions · ~36,000 deletions
  • ~3,300 issues closed
  • 450+ community contributors

The full changelog is scoped v2026.7.1...v2026.7.20 — i.e. everything from the v0.18.0 date-tag forward, which is why the v0.18.1 and v0.18.2 patch windows fold in here.

The speed spine

The headline theme is latency, attacked on several fronts:

  • Cold start: the “Initializing agent…” step dropped from ~4.3s to ~0.9s (~80%).
  • Streaming: reasoning models stream thinking live by default; response boxes paint per token instead of per line.
  • Desktop rendering: incremental block lexing cuts splitter CPU 14x for streaming markdown, review-pane diffs are virtualized (no more full-Shiki freeze on large diffs), and session switching no longer thrashes layout. A systematized perf-benchmark harness replaced ~12 one-off scripts.
  • TUI: markdown renders incrementally, per block.
  • Off-critical-path work: Discord capability detection moved behind a 24-hour disk cache.

Beyond speed

The official notes ship a large surrounding feature set. The ones the community summary called out, plus notable extras:

  • Terminal billing/subscription and /topup, scheduled-change banners with undo, matching desktop billing tab.
  • Password managers — Bitwarden + 1Password via the SecretSource interface, multi-vault with precedence, per-variable provenance and conflict warnings.
  • Smart approvals — LLM-based per-command verdicts on by default, deny rules that hold even in yolo mode, /deny <reason> feedback loop.
  • Subagent visibility + durabilitytail -f live transcripts, durable background completions, human-readable per-child logs.
  • Delivery guarantee — durable state.db response ledger, cross-channel redelivery on reboot.
  • Providers/models — Fireworks AI promoted to a first-class #2 provider (with cost estimation), plus DeepInfra, Upstage Solar, GPT-5.6 (Sol/Terra/Luna + Pro), grok-4.5 GA, kimi-k3, claude-fable-5, claude-sonnet-5, and tencent/hy3; LM Studio JIT local model loading.
  • Reasoning/MoA — new max and ultra effort levels across all surfaces, per-model and per-task effort overrides, per-preset MoA fanout cadence.
  • Multiplex gateway — one bot token can route specific guilds/channels/threads to different profiles, each with isolated config, skills, memory, and secrets; a hardening wave prevents one misconfigured profile from taking down the whole gateway.
  • Sessionshermes sessions export to Markdown/Quarto/HTML/prompt-only/trace/Hugging Face, with --redact, age/workspace/platform filters, and bulk archive.
  • Security hardening — Vertex credentials scoped through the profile secret scope, GOOGLE_APPLICATION_CREDENTIALS stripped from subprocess env, webhook body caps, atomic 0o600 OAuth token writes closing a TOCTOU, and computer-use subprocess env sanitized across five spawn sites.

Notably, the dynamic-workflow orchestration skill was reverted (not shipping in this release) per the “Reverted Features” section — worth tracking against how the wiki documents dynamic workflows on the Claude Code side, since the two are independent implementations.^[inferred: the notes state the revert but not the reason]

Try It

  1. hermes update to v0.19, then read the full changelog on GitHub (github.com/NousResearch/hermes-agent/releases/tag/v2026.7.20) and confirm the v2026.7.20 tag.
  2. Run /subscription in the terminal to check your Nous plan, allowance, and upgrade preview; /topup to add credits — no dashboard trip needed.
  3. Wire a password manager: configure the SecretSource interface for Bitwarden or 1Password so secrets resolve from your vault instead of a plaintext .env.
  4. Leave smart approvals on and add a deny rule for anything you never want run; use /deny <reason> when it flags something so the agent course-corrects.
  5. Fan out a background task with delegate_task and tail -f the returned transcript file to watch the subagent work live.

Open Questions

  • The commit/contributor/PR tallies, TTFT numbers, and feature list are confirmed against the official GitHub release notes (fetched 2026-07-20). The specific ~4.3s→~0.9s cold-start figure is a quoted example from the notes; whether it holds on lower-spec hardware is unstated.
  • The dynamic-workflow orchestration skill revert is stated without a reason in the notes — worth re-checking whether it re-lands in a later patch, since the notes flag one other reverted feature (plugin pre_tool_call approve escalation) as having re-landed and shipped here.
  • Whether the v0.19.0 date-tag 2026.7.20 follows the prior “v0.NN.0 plus vYYYY.M.D” pattern is consistent with the v0.18.0 tag 2026.7.1.