Hermes brings its workspace to a browser through the gateway

A conversation moving from a bot to a browser needs a session owner that both interfaces recognize. That is the architectural change highlighted in Hermes Agent v0.23.0, dated November 5, 2026 in the release notes: the user's own gateway serves browser access to the Desktop workspace.

The notes describe a gateway responsible for each session, with terminal interfaces, Desktop, editors, bots and cron connecting to that shared owner. The intended benefit is continuity across interfaces instead of each surface running a separate agent for the same conversation. That distinction matters when work moves between devices or communication channels.

Web access is disabled by default. Updating the software should therefore not be confused with automatically exposing the workspace on a network. Enabling access is a separate configuration decision, and authentication and network reach need to match the intended deployment.

I would check the hand-off itself: the conversation shown in each interface, the gateway owning it and the users allowed to reach it. The release notes establish available behavior, not a completed migration of an existing installation. The operational decision left is whether to enable browser access, with authentication and network reach set for the people who need that conversation.