{"slug": "nous-research-adds-persistent-multi-gateway-control-to-hermes-desktop", "title": "Nous Research adds persistent multi-gateway control to Hermes Desktop", "summary": "Nous Research has added persistent multi-gateway connections to Hermes Desktop, enabling users to manage agents running locally, in Hermes Cloud, over SSH, and on remote servers from a single interface. The feature, shipped in Hermes Agent v0.21.0 and highlighted in a September 2nd post on X, stores a named registry of backends and allows users to add, test, rename, and remove connections from a Gateways settings page. The release was directed by Nous Research co-founder Ryan Teknium, who contributed to roughly 1,340 merged pull requests during the v0.21.0 development window.", "body_md": "# Nous Research adds persistent multi-gateway control to Hermes Desktop\n\n**The v0.21.0 registry keeps local, cloud, remote and SSH agents visible while background jobs continue streaming.**\n\nBy [Ryan Merket](/author/ryan-merket)\n· Published\n\nPrimary source: [Nous Research on X](https://x.com/NousResearch/status/2095199772336341480)\n\n## Why it matters\n\nHermes Desktop is becoming a control plane for distributed AI agents, letting one operator manage separate machines, credentials and workloads without collapsing their security boundaries.\n\nNous Research has added persistent multi-gateway connections to Hermes Desktop, giving users one interface for agents running locally, in Hermes Cloud, over SSH and on remote servers. The lab highlighted the feature in a [September 2nd post on X](https://x.com/NousResearch/status/2095199772336341480), two days after shipping it as part of Hermes Agent v0.21.0.\n\n[https://x.com/NousResearch/status/2095199772336341480](https://x.com/NousResearch/status/2095199772336341480)\n\nThe release was directed by Nous Research co-founder [Ryan Teknium (@Teknium1)](https://x.com/Teknium1), whose GitHub profile describes Hermes Agent as his current focus. Teknium has worked on Nous Research's open-weight models, datasets, reinforcement-learning environments and synthetic-data pipelines, then pushed Hermes beyond the lab's model releases into a full agent product. Nous Research's [release notes](https://github.com/NousResearch/hermes-agent/releases/tag/v2026.8.31) credit him with work spanning Bot Mode, persistent cron memory and the desktop MCP management interface, alongside roughly 1,340 merged pull requests during the v0.21.0 development window.\n\nThe multi-gateway feature is an operational layer for that broader agent system. Hermes Desktop now stores a named registry of every backend it can reach, including the app-managed local runtime, self-hosted remote gateways, SSH installations and hosted Hermes Cloud instances. Users can add, test, rename and remove those connections from a single Gateways settings page.\n\nAccording to the [multi-connection documentation](https://hermes-agent.nousresearch.com/docs/user-guide/multi-connection-desktop), every profile discovered on a registered gateway appears as an agent in a combined roster. If a profile called `research`\n\nexists on more than one machine, Hermes adds the device name to its handle, producing identifiers such as `@research-homelab`\n\n. That prevents two identically named agents on separate machines from becoming indistinguishable in the desktop interface.\n\n### One desktop, several execution environments\n\nThe connections persist across restarts, but Hermes does not keep every remote socket open without reason. It enumerates agents through REST calls, then opens a backend and WebSocket when the user selects an agent. Each gateway-and-profile pair receives its own connection, and an agent already working in the background can continue streaming output while the user views another gateway.\n\nThat design matters for people spreading agents across machines with different resources or permissions. A coding agent could run on a workstation with access to a repository, while a monitoring bot stays on an always-on server and another profile runs in Nous Research's hosted service. Hermes Desktop presents those agents together without moving their files, credentials, memory or tools onto the user's current machine.\n\nThe feature is separate from Hermes' existing gateway multiplexing. Multiplexing lets one process serve several isolated profiles on the same host. The new desktop registry connects one application to gateways across several hosts. Nous Research's documentation preserves that boundary because each remote machine remains its own execution and trust context.\n\nSessions still operate within one selected gateway at a time. Files, cron jobs, messaging channels, settings and memory remain scoped to the active gateway and profile. Bot Mode can display the combined roster, but direct mentions and delegation stay gateway-local by default. Cross-gateway execution requires an explicit bridge, reducing the risk that an instruction intended for a local agent reaches a remote machine with different credentials or filesystem access.\n\nHermes also keeps unreachable gateways in the roster with an error marker instead of dropping their agents. SSH connections remain dormant until used, avoiding surprise tunnels, while hovering over an agent can pre-warm its backend before selection.\n\n### Managing the fleet becomes part of the product\n\nThe registry extends into updates and plugins. Hermes Desktop can send an update command to eligible local, remote and SSH instances in parallel, while Hermes Cloud entries are skipped because Nous Research manages those versions. A failed or unreachable machine reports its result independently rather than blocking the entire batch.\n\nPlugin developers get the same multi-gateway model through APIs that list registered connections, return the combined agent roster and activate a specific gateway-profile pair. Tokens stay outside the renderer and plugin layer in owner-only files, with optional operating-system keychain encryption.\n\nThe timing fits the larger direction of the [August 31st v0.21.0 release](https://github.com/NousResearch/hermes-agent/releases/tag/v2026.8.31). Nous Research built Bot Mode into the desktop app, added durable agent-to-agent chats, gave scheduled jobs persistent memory and allowed users to steer subagents while they run. Persistent gateway connections make those features usable across a collection of machines instead of confining the agent roster to one installation.\n\nHermes Desktop runs on macOS, Windows and Linux and uses the same open-source, MIT-licensed agent core as the command-line interface. Remote installations still need a reachable `hermes serve`\n\nbackend, except for SSH connections where the desktop app can start the service through the tunnel. Nous Research is leaving the infrastructure choices with the user while consolidating their controls into a desktop interface that increasingly resembles an operations console for persistent agents.", "url": "https://wpnews.pro/news/nous-research-adds-persistent-multi-gateway-control-to-hermes-desktop", "canonical_source": "https://runtimewire.com/article/nous-research-hermes-desktop-persistent-multi-gateway-connections", "published_at": "2026-09-03 00:33:34+00:00", "updated_at": "2026-09-03 00:52:20.099574+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "ai-products"], "entities": ["Nous Research", "Hermes Desktop", "Hermes Agent", "Hermes Cloud", "Ryan Teknium"], "alternates": {"html": "https://wpnews.pro/news/nous-research-adds-persistent-multi-gateway-control-to-hermes-desktop", "markdown": "https://wpnews.pro/news/nous-research-adds-persistent-multi-gateway-control-to-hermes-desktop.md", "text": "https://wpnews.pro/news/nous-research-adds-persistent-multi-gateway-control-to-hermes-desktop.txt", "jsonld": "https://wpnews.pro/news/nous-research-adds-persistent-multi-gateway-control-to-hermes-desktop.jsonld"}}