Hermes Agent 0.23.0 puts its full desktop workspace in a browser, served by the user’s own gateway. The stable release also brings conversations from the CLI, desktop, editors, bots and scheduled jobs under one gateway, aiming to make them behave like one connected workspace rather than a collection of near-identical agents.
Nous/Hermes Watch analysis
What happened
NousResearch’s release notes date version 0.23.0 to 5 November and call it the Hearth release. The project says it rolls up and documents changes from versions 0.22.1 to 0.22.7 as well as the new release. The official release notes describe roughly 1,950 merged pull requests since 0.22.0.
Our top picks
- Open the desktop workspace in a browser
The web app serves chats, group chats, plugins and settings from a user’s gateway; it is off by default. - Give one gateway ownership of conversations
CLI, desktop, editors, bots and cron attach to the same session, reducing the chance of duplicated or missing messages. - Connect multiple machines in one desktop window
Users can keep local and remote gateways open together, with group chats able to mix bots across machines. - Rewind a conversation
CLI and TUI users can return to an earlier message and edit or fork from there without changing the original session. - See images in the terminal
The CLI and TUI can display pasted images and screenshots, with support varying by terminal. - Put prices and limits on paid tools
Paid MCP calls can show their cost and running total, with Hermes asking before a chat exceeds its limit. - Update plugins in bulk or automatically
Users can update plugins together or opt into automatic updates, with changes that would break a setup held back.
Why it matters
The browser workspace is the headline, but the deeper change is shared continuity: a conversation can move between tools without each surface running its own copy of the agent. That could make Hermes easier to use across a desktop, terminal and remote machine, while the cost prompts give paid tool calls a more visible boundary.
This is a large release, so the upgrade notes deserve a proper look. The built-in browser tools have been replaced by browserexec; prompts, skills or tool lists that name the removed tools need updating. The desktop app also now requires macOS 13 or later and 64-bit Windows.
Our read
This is a substantial change to how Hermes is put together, not just a fresh coat of paint on a patch release. Shared sessions and the browser workspace are meaningful improvements for people who already use Hermes in several places. Before upgrading, check whether your own browser workflows rely on the removed tools. The agent can move into a browser tab; your old tool names cannot.
What to watch
- How the gateway-based browser workspace performs on local networks and public URLs.
- Whether shared sessions prevent duplicate or missing messages across the supported surfaces.
- How users adapt prompts and skills to browserexec.
- Whether plugin auto-updates and spend limits behave as the release notes describe.
Discussion spark: Would you trust one gateway to keep conversations consistent across every Hermes surface, or would you rather keep each tool isolated?
Sources and evidence
- Releases · NousResearch/hermes-agent · GitHub (Publication date not supplied)
Nous/Hermes Watch is independently operated by WittyWires. It is not affiliated with, endorsed by, or operated by Nous Research.