The Quicksilver Summer

Five months. Roughly two dozen tagged releases. One long arc from "a new open-source agent" to a platform trusted with your finished answer. Between March and July 2026, Hermes Agent went from its first public tag to the Quicksilver release, and the pace never once let up.

March: the gateway opens

On March 12, Hermes Agent shipped v0.2.0, its first tagged release since the pre-public v0.1.0 foundation. The release note led with the numbers: 216 merged pull requests from 63 contributors, resolving 119 issues, in just over two weeks. A small internal project had become a community project. The tag landed with the gateway and the skills ecosystem that would define the project — and the community kept coming. The next week brought 300 merged PRs in a single sprint, with streaming output, native browser tools, and the first plugin architecture. By month's end Hermes had user profiles, MCP server mode, Docker support, and Nous Portal's 400+ models.

Spring: breadth, then reach

April was about surface area. The tool gateway opened web search, image generation, text-to-speech, and browser automation to subscribers. A new Ink-based TUI arrived, built on a pluggable transport architecture. Native providers — AWS Bedrock, Google AI Studio, Anthropic — joined, and Android support shipped via Termux. May was the reliability and scale month. The Foundation release brought pip install hermes-agent and a native Windows beta, then the Velocity release crossed 100,000 GitHub stars. The unruly 16,000-line run_agent.py was split into focused modules, and session_search was rebuilt to be no-LLM and instant.

June shifted from raw growth to polish. The Surface release delivered a native desktop app for macOS, Linux, and Windows, plus a full browser admin panel. The Reach release added iMessage via Photon, the Raft agent network, background subagents, and a rebuilt Skills Hub. Then July's Judgment release closed every tracked P0 and P1, added first-class Mixture-of-Agents models, and made "done" evidence-based — with verification evidence and completion contracts behind every /goal.

July: the Quicksilver release

v0.19.0, published July 20 under the tag v2026.7.20, is where the window's themes converged. Since v0.18.0 the project had recorded roughly 2,245 commits and 1,065 merged PRs — but Quicksilver's story is narrow and sharp. First-turn time-to-first-token dropped about 80%, from a cold ~4.3 seconds to ~0.9, by pulling Discord capability detection off the critical path and removing blocking startup work.

The other headline is durability. Before Quicksilver, a gateway could die after generating an answer but before the platform confirmed delivery — the response lost, the turn paid for. The new delivery-obligation ledger records every final response in state.db around the send and redelivers on the next boot, closing a silent-loss window across Telegram, Discord, and Slack. Smart approvals became the default, with an LLM reviewing each flagged command afresh. Bitwarden and 1Password joined as pluggable secret sources, and one multiplexed gateway could finally route channels to isolated profiles.

The through-line

Read the five months as one story and the theme is clear: Hermes was always trying to remove friction from working with it. The gateway and skills made the agent reachable; the providers gave it options; the desktop, TUI, and admin panel gave it surfaces; and Quicksilver made it fast enough and durable enough to trust with an answer you can't afford to lose. For an MIT-licensed project that started the window at its first public tag, that is a remarkable first act.