AI News
All stories
Official

Hermes Agent v0.23.0 adds browser-tab Desktop webapp and one gateway for all sessions

Nous Research's Hermes Agent v0.23.0 serves the full Desktop workspace in a browser tab and routes the CLI, TUI, Desktop, editors, bots and cron through one gateway per machine.

Products · · 3 min read

Nous Research's Hermes Agent v0.23.0, released November 5, 2026, lets users open the full Desktop workspace in a browser tab. A new Webapp serves the same chats, Group Chats, plugins and settings from the user's own gateway. It can be reached from any browser on the local network or behind a public URL with sign-in. The Webapp is off by default. Users turn it on with webapp.enabled or the Web Access setting in Desktop, and the Docker image and Nix package ship it. The release notes say the Webapp is single-user: a signed-in tab acts as the user, so its sessions are the same ones native Desktop shows.

The notes describe a change in how sessions are owned. Before this release, they say, the CLI, TUI, Desktop, ACP editors, messaging bots and cron could each run their own copy of the agent against the same chat. That is how messages got written twice or went missing between surfaces. Under the new design, each machine runs one gateway that owns every session, and each surface attaches to it as a client. A chat therefore has one queue and one history. The notes also say a queued prompt can be steered or edited from Desktop without running twice.

The notes place this model in v0.22.0, not v0.23.0. Since v0.22.0, they say, the classic CLI, TUI, Desktop, API, ACP editors, bots and cron all run sessions through one gateway. This cycle fixed what that broke, including slash commands, /retry, clarify cards, reasoning display, usage and ACP sessions. The notes do not report independent testing of either version. The fixes are cited to the project's own pull requests.

Other additions are described in the project's own words. Bot Mode Group Chats can route a message that names nobody to a lead bot or an automatic router. Bot-to-bot exchanges are capped at max_hops, default 4, after the last human message. Plugins gained an opt-in auto-update switch, and the notes say updates that would break a setup are held back. The plugin catalog grew from about 600 to over 1,050 entries. A new Verified tier marks plugins that Nous describes as made by the company whose product they integrate. Paid MCP tools can declare a per-call cost and a per-chat spend limit. The notes say Hermes asks before a chat goes over its limit, even in YOLO mode.

Several changes break existing setups, and the notes flag them. The old built-in browser tools were removed, and browser automation now runs only through browser_exec. Prompts, skills or toolset lists that name the old tools need updating. Desktop now requires macOS 13 or later and 64-bit Windows. The app moved to Electron 44, which no longer runs on macOS 11, macOS 12 or 32-bit Windows. The hermes mcp serve command became hermes mcp-serve. The notes say MCP clients that launch Hermes as a server must change their command themselves, since nothing rewrites it for them.

The Webapp's security claims rest on the release notes alone. The notes say the page sends a Content-Security-Policy, that a signed-out status endpoint reveals no profile names, and that the Webapp trusts only its own loopback port for CORS and WebSockets. They do not describe how sign-in for a public URL works. They also do not say what protects a single-user session once it is exposed beyond the local machine.

The notes count about 10,080 commits, about 1,950 merged pull requests and 666 contributors since v0.22.0. They say the release also rolls up and documents the v0.22.1 through v0.22.7 patch releases, dated October 14 to November 3.

What changed

Hermes Agent v0.23.0 adds an opt-in Webapp that serves the full Desktop workspace in a browser tab, and the notes place the single-gateway session model in v0.22.0.

Type: New capability · Takes effect: Thursday, November 5, 2026 · Applies to: Hermes Agent v0.23.0, webapp.enabled, Desktop, Docker image, Nix package

Why it matters

Teams running Hermes agents on several machines get one shared session history, but a browser-accessible workspace adds a network surface that needs sign-in controls.

What you can do

Leave webapp.enabled off unless remote browser access is needed, and review sign-in settings before turning it on.

Original source

Where we saw it

1 source

Hermes Agent releases

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it. How it works