Hermes Agent 0.23.0 lets users run the desktop app in a browser from their own gateway
Nous Research’s Hermes Agent 0.23.0 brings the desktop app’s workspace to the browser from the user’s own gateway. The feature is off by default, and some users will need to make changes when upgrading.
Nous Research released Hermes Agent 0.23.0 on 5 November, announcing it in GitHub release notes and on X.
Hermes Agent is a harness: a program that controls the agent, gives the model tools and runs its steps. It can be used from the command line (CLI), a terminal text interface (TUI), the desktop app, editors, messaging bots and scheduled tasks. About 1,950 pull requests have been merged since version 0.22.0, the release notes say.
A browser workspace and one gateway
The main news is Webapp. The user’s own gateway, the Hermes service running on the user’s machine, serves the desktop app’s full workspace to a browser. The browser shows the same chats, Group Chats, plugins and settings. The workspace can be used on the user’s own network or, after sign-in, through a public URL. Teknium of Nous Research wrote on X that the agent can now be accessed through a browser from anywhere.
Webapp is a single-user service: a signed-in tab acts as the user. Webapp is off by default. Users can turn it on with the webapp.enabled setting or with Web Access in the desktop app’s settings.
Webapp builds on a change that gives one gateway control of every chat on a machine. Previously, different interfaces, bots and scheduled tasks could each run their own agent in the same chat, so messages were sometimes saved twice or lost. Now they attach to the gateway as clients, so each chat has one queue and one history. The release notes say this model has been in use since version 0.22.0, and this release fixes features it broke.
Paid MCP tools, such as 3D and media generators, can now report the price of a call. The approval prompt shows the price and the chat’s running total. Hermes asks for permission before a chat exceeds its spending limit, even in YOLO mode, which otherwise skips approvals.
In the TUI and the classic CLI, users can return to an earlier message with the /rewind command or by pressing Esc twice. They can edit the message and resend it, or start a new session from it, and the original session stays unchanged. The CLI and TUI also display attached images and screenshots in the chat, and plugins can update automatically, although this setting is off by default.
Upgrading requires changes for some users
The old browser tools, such as browser_navigate and browser_click, have been removed. Browser automation now works only through browser_exec, so prompts, skills and tool lists that use the old names must be changed.
The desktop app now requires at least macOS 13 or 64-bit Windows because it moved to Electron 44.
The hermes mcp serve command is now hermes mcp-serve. If an MCP client launches Hermes as a server, its command must be updated by hand.
The Word, PowerPoint and Excel skills have been merged into a single microsoft-office skill. Old copies stay on disk until the user deletes them.
The approval step now also asks for permission for pipes such as curl … | sudo bash, and Hermes masks more types of secrets than before.
New installations now fetch the latest stable version instead of the development branch. Detailed instructions are in the release notes on GitHub.
Read more: How an agent works · Agent map