Two ways to tell the story of Hermes’s day. The first plays well on social: a plugin that draws the session as a space station, the main agent at the centre and the subagents as modules in orbit. The second is duller and more important: the stable version is 0.22.2, published on 15 October, and it fixes a release built from the wrong commit. Together they say the same thing: Hermes is no longer a demo that updates as a surprise, but a product with release channels and tools for looking inside what it does.

Seeing the work behind the chat

Agent Station is a community plugin for Hermes Desktop, not an official Nous product: the catalogue card points to Muhammed Enes Alpler’s repository, MIT licence, revision pinned to a commit. It shows what happens in the chat in the foreground: one page draws the agent and the subagents started with delegate_task — task, files touched, response, cost —, one tab lists background shell commands, a third retraces file changes after each request. Two details matter more than the aesthetics: it is read-only, opening the state database in read-only mode and registering only GET routes; and it requires Hermes 0.21.7 or higher, tested up to 0.22.2. Anyone coming from Subagent Watch, the project’s old name, has to uninstall it first, or ends up with two entries in the sidebar.

The release that fixes the release

The 0.22.2 announcement is a small document of engineering hygiene. 0.22.1 had been compiled from the wrong commit: it contained gateway work that had not been released yet, and the Microsoft Store app could get stuck on “Connecting”. 0.22.2 is the release it should have been. Two fixes show up in daily use: the gateway restarts after a reboot — on Linux a reassigned PID could be mistaken for an active gateway, and a gateway supervised by systemd or Docker refused to start (PR #138594) — and long turns with local models survive a laptop suspending, with streaming, timers that ignore sleep and compression without timeouts (PR #138560). One known defect remains: sessions started under gateway 0.22.1 cannot be deleted in 0.22.2.

Channels, not surprises

Answering a report on an already merged pull request, Teknium explained that channels exist so users are not forced to update at every change: anyone who wants the very latest code moves to main, anyone who wants stability stays on tags. It is the difference between a project you follow and software you use: today’s work on main — a handful of fixes, no new tag — will not reach people on stable before 0.23.0. And that is fine.

Seen that way, the 107,000-line dungeon crawler “generated by agents” is the least interesting part of the day. The interesting part is that someone built a window for watching agents work, and that the project learned to say: this release was wrong, here is the right one.

Verified sources: GitHub, NousResearch/hermes-agent release v0.22.2 (15 October 2026); Hermes Agent plugin catalogue, agent-station card, catalogue built on 20 October 2026; Hermes changelog, PR #140760 “feat(plugin-catalog): add agent-station plugin”, merged 19 October 2026; @Teknium post on X, 20 October 2026 (from Echo’s report, not verifiable against an independent source).