Hermes Agent v0.23.0 brings Desktop to the browser

Hermes Agent v0.23.0 brings its Desktop workspace to a browser, adds conversation rewind and introduces spending controls for paid tools. Nous Research published the Hearth Release on November 5, 2026. It targets people running Hermes across computers and interfaces, with several compatibility changes existing users should check before upgrading.

The official release notes also collect changes from versions 0.22.1 through 0.22.7. Some features therefore reached users before this release. We reviewed the release and documentation; we have not installed or independently tested this version.

A browser workspace with access to your host

The Webapp serves chats, files, Git review, scheduled jobs and terminals from a Hermes gateway. It is disabled by default and is separate from the older Web Dashboard. A local browser session still runs its work on the gateway, rather than moving execution into the browser.

The Desktop documentation warns that a signed-in Webapp user can run commands with the host account’s permissions and reach its files and credentials. Remote access needs a sign-in provider. The documentation recommends a trusted VPN or SSH tunnel, and strongly recommends HTTPS for remote use.

Plain HTTP on a remote address also loses browser features such as microphone and clipboard access. Some desktop features, including global shortcuts and the native updater, remain in Electron. Check the functions you actually need before replacing the native app with a browser tab.

Browser access is a separate route from the Hermes Mobile beta waitlist we previously covered. The mobile invitation does not establish immediate access or an on-device runtime.

Several machines, without merging their work

Hermes Desktop can maintain connections to local, remote, SSH and Cloud backends simultaneously. The multi-instance guide says sessions and background work remain connected while you look at another gateway. That matters when a laptop and a server handle different jobs: switching the view should not require rebuilding the connection each time.

The important boundary is ownership. Chats, files, memory and scheduled jobs stay with their gateway and profile. Putting several agents in one window does not put all their files or credentials in one shared environment. Direct bot mentions and delegation remain local to their gateway by default.

A remote backend must be running and reachable. SSH connections have a documented startup flow, but adding an ordinary remote URL does not start that server. Treat connection setup and agent execution as separate checks.

Rewind changes the conversation

The slash-command reference explains two different outcomes for /rewind. Editing an earlier prompt archives the later messages and sends the revised prompt from that point. Forking creates a new branch while preserving the original session. Cancelling the selection removes nothing.

That distinction matters when comparing two approaches. Fork if you want to keep the original attempt available. Edit when you want the current conversation to proceed from a corrected instruction. Neither operation should be mistaken for proof that a previous tool action has been reversed.

File recovery still needs its own plan

Hermes documents file recovery separately through checkpoints and /rollback. Checkpoints are opt-in, with storage costs and coverage limits. Before relying on a restore, inspect the available checkpoint and its diff.

There are concrete exclusions. A parent checkpoint does not capture uncommitted changes inside nested Git repositories. Container-backed file paths also do not receive the host checkpoint protection described in the guide. Keep separate backups for work outside the supported coverage. A conversation that looks rewound can still sit beside files changed during the original attempt.

Paid-tool limits are estimates, not an invoice

The MCP documentation lets a server configuration declare tool costs and a per-chat spending limit. Hermes uses those declared figures to show expected charges and request approval before a call crosses the limit, including when YOLO mode is enabled. If an unattended run cannot obtain approval, the over-limit call is refused.

The counter has limits of its own. It records declared costs, uses the upper end of a range, and can count a started call even when the server fails before receiving it. Totals are kept in memory and reset when Hermes restarts. They are not the provider’s final billing records.

Set a limit where paid tools are configured, then reconcile actual charges with the provider. A missing or zero spend limit leaves that server without this budget guard. Do not assume installing the update automatically caps every paid service an agent can reach.

Check compatibility before upgrading

The release requires macOS 13 or later and 64-bit Windows for Desktop. Existing browser-tool instructions need to use browser_exec, and MCP clients launching Hermes must replace hermes mcp serve with hermes mcp-serve. Review those integrations before updating an installation used for regular work.

The practical value is easier access to ongoing work, with clearer ways to revisit instructions and watch tool spending. Start with one noncritical workflow. Confirm which machine runs it, what the browser can access, and which recovery and billing controls actually apply before trusting the same setup with more consequential jobs.

Featured image: AI-generated editorial illustration by ByteForward. Hermes Agent wordmark: Nous Research (MIT license). Conceptual artwork, not a product screenshot.