What happened
Nous Research released Hermes Agent v0.23.0, titled “The Hearth Release,” on November 5, 2026. The release notes say it rolls up and documents the v0.22.1–v0.22.7 patch releases. They report approximately 10,080 commits, 1,950 merged pull requests, 8,720 files changed, 725,200 insertions, 201,400 deletions, 850 issues closed and 666 contributors since v0.22.0. These are the release’s own repository statistics, not an independent assessment of the changes.
The headline is a Webapp that serves the full Desktop workspace from a user’s own gateway. The notes describe the same chats, group chats, plugins and settings being available in a browser on the local network or behind a public URL with sign-in. Docker and Nix packages include it. It is disabled by default; users can enable it through webapp.enabled or Web Access in Settings. The release notes do not specify hosting costs or operational requirements for exposing it publicly.
A second architectural change is that one gateway on each machine owns every session. Previously, the CLI, TUI, Desktop, editor integrations using ACP, messaging bots and cron could each run a separate agent against the same chat. According to Nous, that could produce duplicate messages or messages missing between interfaces. In v0.23.0, the interfaces attach as clients to the gateway; a conversation has one queue and one history. Desktop can steer or edit a queued prompt without running it twice. The notes present this as the new session model, but do not provide comparative reliability measurements.
Desktop can now keep multiple gateways connected, including a local computer and SSH or remote gateways. Terminal tabs run on the host where they were opened, and a group chat can mix bots from different machines. Group Chats also gain routing: a lead bot or automatic router can choose who answers an unaddressed message. Scheduled jobs can post into a room, rooms can hold a purpose and shared notes, and bots are prevented from pinging one another in endless loops.
Other documented changes include inline image display in CLI and TUI, and conversation rewind: users can select an earlier message, edit and resend it, or fork a session while leaving the original unchanged. Plugins can be updated together with hermes plugins update; opt-in auto-update is available across CLI, chat, Desktop and dashboard, with updates that would break a setup held back. The plugin catalog grew from about 600 to over 1,050 entries, and a Verified tier marks vendor-built plugins. Paid MCP tools can declare call prices; approval prompts show the price and running total, and Hermes asks before a chat exceeds its spending limit, including in YOLO mode. The supplied release notes give no general price for Hermes itself or paid MCP services.
What the archive adds
The archive has tracked Hermes Agent as a self-hosted, MIT-licensed open-source agent and recorded the v0.22.5 release: Nous Research’s Hermes Agent: MIT-licensed, self-hosted open-source agent, now at v0.22.5. It also records v0.22.6 adding migration support for Grok Bot and OpenBot setups: Hermes Agent v0.22.6. This is a new release on a known product story, with a notably broader session and workspace architecture; it is not a restatement of either earlier change.
Trend signal
This release supports harness architecture outlives model choice: its headline is not a new model, but a gateway and session structure connecting multiple clients, machines and workflows. That makes the surrounding runtime more consequential to day-to-day use. The release does not establish that this architecture is more durable or reliable than alternatives; it documents Nous’s product direction and implementation.
Why now
The release notes frame v0.23.0 as the next stage after v0.22.0, which they say got newcomers through the door. The new version consolidates and documents the v0.22.1–v0.22.7 patch releases. That is the timing explanation the source provides; it does not identify a market event or external deadline driving the release.
Why it matters
A shared gateway can make an agent workspace less fragmented: a developer can move from terminal to Desktop or editor without treating each surface as a separate conversation. For teams, a single owner of session history and queues may also simplify supervision and reduce confusing duplicate runs. Multi-gateway Desktop support extends that model across local and remote machines, while room-level routing could help teams coordinate bots without manually choosing each responder.
These are operational promises, not demonstrated outcomes. Builders should evaluate whether the gateway fits their deployment model, particularly before exposing the browser workspace publicly. The spend display and threshold confirmation for paid MCP calls are directly relevant where tools incur usage charges: teams can see an individual call’s declared price and running chat total before approving further spend. But the release supplies no evidence of cost savings, security review or measured reliability. Treat the update as a set of capabilities to test against your workflow, not proof that it will improve it automatically.
Limits and uncertainty
The release notes are the supplied evidence for this decision. They describe features and give aggregate repository activity, but do not provide independent verification, adoption numbers, performance tests or before-and-after measurements for duplicate or missing messages. The notes do not establish the security properties of a publicly reachable Webapp, or detail its authentication and deployment requirements beyond mentioning sign-in. They also do not state Hermes’s overall price, supported paid-tool pricing coverage, or how spend limits behave beyond the stated confirmation before a chat exceeds its limit. Compatibility, migration effort and availability in particular configurations should be checked in the project documentation before rollout.
Reader takeaway
Hermes v0.23.0 makes the gateway the center of a shared, multi-interface agent workspace and adds a browser interface plus declared-cost controls for paid MCP tools. If you use Hermes, assess the gateway and Webapp against your deployment and access requirements, then test session continuity and spending thresholds before relying on them in production.