Hermes v0.23: Browser Workspace and Breaking Upgrade Changes

Hermes Agent v0.23.0 brings the Desktop workspace to a browser, expands shared gateway sessions and adds controls for paid MCP tools and scheduled jobs. The November 5 Hearth release also removes old browser tools and changes the command used to run Hermes as an MCP server.

For teams running persistent agents, those migration details are the reason to plan this upgrade. This guide separates the official release changes from my operational recommendations. It also consolidates the deferred v0.22.1–0.22.7 patch notes into one release assessment.

What changes with browser access?

The new Webapp serves the Desktop workspace from your own gateway, including chats, Group Chats, plugins and settings. The release says it ships in the Docker image and Nix package. Browser access is off by default, enabled through webapp.enabled or Web Access in Settings. The notes describe access on your network or behind a public URL with sign-in. Release highlights

My recommendation is to begin with private access. Confirm which gateway and profile the browser reaches, how sign-in works, and which sessions and tools the account can use before making it reachable outside your network. A browser interface does not itself create an isolation boundary between connected business systems.

Desktop can also keep multiple gateways connected at once. Terminal tabs remain attached to the host where they were opened, and a Group Chat can contain bots from different machines. Make the host and profile visible in your operating procedure before running a command that changes files or infrastructure.

What does one gateway mean for conversations?

Hermes describes one gateway owning each session while CLI, TUI, Desktop, editors, messaging bots and cron attach as clients. The aim is a shared queue and history across surfaces, reducing duplicate or missing messages caused by separate agent runtimes. The version-pinned gateway documentation details the canonical session identity and gateway-owned execution.

This builds on consolidation already discussed in our v0.22 guide. The new release is worth a separate review because browser access, operational controls and breaking tool migrations change how that architecture is used.

Test continuity with a harmless conversation. Open it from two supported surfaces, send one prompt, and confirm one response and one history entry. Then reconnect a client and verify that it reaches the same session. These are proposed acceptance checks, not a claim that FindMilan has tested your installation.

Which upgrade changes can break integrations?

Three changes deserve a configuration review before rollout. Official upgrade notes

• Browser automation: agent-browser and the ten old browser_* tools are removed. Custom prompts, skills and toolset lists that name them must move to browser_exec. The exact-release browser documentation explains its Python-based browser interface and companion tools. Review the semantics of each workflow rather than merely replacing a tool name.
• Hermes as an MCP server: hermes mcp serve becomes hermes mcp-serve after moving into a plugin. Update external MCP client launch commands manually. This differs from Hermes connecting to an external MCP server, covered in the MCP documentation.
• Desktop compatibility: the Electron 44 move requires macOS 13 or later and 64-bit Windows. Check the actual machine before distributing the Desktop upgrade.

The release also combines Word, PowerPoint and Excel skills into microsoft-office; old copies remain on disk until removed. Inventory custom skill references and avoid deleting locally curated material as part of an automatic cleanup.

What changes for paid tools and plugins?

Paid MCP tools can declare a call price. Hermes shows that price and the chat’s running total in the approval prompt, and asks before exceeding the chat limit, including in YOLO mode. This is a useful operator control, but a tool’s declared cost is not a substitute for checking provider billing and account limits. Paid-tool controls

hermes plugins update can update plugins together, while automatic updates are opt-in. The release says incompatible updates are held back. Its Verified tier identifies vendor-built plugins; that label should not be treated as a guarantee that every action suits your organization’s permissions or data rules.

For production, review the installed version, requested permissions and a small representative task before enabling automatic updates. Keep plugin changes separate from a gateway migration when that makes failures easier to diagnose.

What should automation operators test?

The release adds cancellation of running cron jobs through the CLI, Desktop, API or agent, plus per-job handling for runs missed while Hermes was offline. Group Chat jobs can post into rooms, with mentions controlling which bots wake. Scheduling changes

Use a disposable job to check cancellation and missed-run behavior. Verify both the job state and its downstream effect. A cancelled agent turn cannot be assumed to recall an email or undo a write that already completed.

The new /rewind flow lets terminal users select an earlier message and edit, resend or fork from that point. Treat this as conversation history control. The announcement does not promise rollback of external actions.

A practical rollout sequence

1. Back up configuration, session data and locally maintained skills. Confirm the backup can be restored independently of the running gateway.
2. Record the installed version, operating system, plugin versions and external MCP launch commands. Search custom skills for removed browser tool names.
3. Upgrade a test installation first. Check Desktop compatibility, one-session continuity, browser automation and an MCP client that launches Hermes.
4. Keep Webapp access private during evaluation. Confirm sign-in, gateway selection and permissions before broadening access.
5. Test a scheduled job, its cancellation and its downstream result. Record failures and recovery steps before resuming business automation.

These checks help answer whether your workflows survived the upgrade. They do not establish universal compatibility or complete security assurance. Model availability and provider charges also remain dependent on the account and route you configure.

For help designing that rollout, my AI consulting service covers agent integrations, permissions and production verification. The AI Web Awards project provides related context on building an AI-enabled platform with explicit application boundaries.

Sources and scope

This article uses the stable v0.23.0 release and documentation pinned to that tag. Daily canary and release-candidate entries are excluded. The earlier retention and plugin guide remains the record for v0.22.3–0.22.4; this guide focuses on the newer stable release and its migration decisions.