Hermes proposes a bot-owned desktop with explicit human takeover and hand-back

Hermes contributor teknium1 opened a Bot Screen proposal on September 12 for a familiar unattended-agent problem: the bot is running on a remote Linux machine, but a person needs to complete a login on the exact screen and browser profile it uses. The proposal combines a per-profile Xfce desktop, a streamed viewer and an explicit control lease. Its most consequential detail is not the live picture. It is that a takeover must stop the agent from reading or manipulating the same screen, including through a separate browser tool. The pull request remains open; this is a reviewed product direction, not an announced packaged feature.

The facts

- The proposed desktop uses TigerVNC over a private Unix socket, with no TCP listener, and separate per-profile display state. - A one-shot WebSocket ticket lasts 30 seconds; the bridge filters keyboard, pointer and clipboard input from viewers that do not own control. - Automatic screen startup is off by default. Starting the screen and installing its host packages are explicit actions. - The revised lease is stored under a file lock so another process cannot keep driving the display after human takeover. - The proposal says an abnormal viewer disconnect retains human exclusion, while normal close can hand control back. - The dock browser and agent browser share a profile; cloud-browser integration, dashboard integration and per-bot OS users are explicitly outside this proposal.

Why it matters

This addresses a real adoption boundary between a remotely useful assistant and a machine that constantly needs its operator to SSH in. Sharing a login session is convenient, but sharing a cursor while someone types credentials is not a safe handoff. The related Realms draft explores another route to separate agent desktops, with its own dependency and setup requirements. Neither proposal should be flattened into a claim that every Hermes bot now has an isolated computer.

Current

Inspected on 2026-09-13. The Hermes Agent release baseline is v2026.9.11 published 2026-09-11T19:20:31Z. The main source was open (not merged) when captured. Proposals, merged mainline changes and packaged releases are different availability states; the linked release baseline does not imply that open proposals have shipped.

Evidence

Primary evidence: NousResearch/hermes-agent PR #108914 (https://github.com/NousResearch/hermes-agent/pull/108914). Supporting context: NousResearch/hermes-agent PR #104567 (https://github.com/NousResearch/hermes-agent/pull/104567); Nous Research — Hermes product documentation (https://hermes-agent.nousresearch.com/docs/). Sources were read directly through public pages or GitHub API bodies. Contributor test results are attributed claims, not independently reproduced results.

Operator take

Evaluate the handoff as an ownership protocol: two viewers, takeover during an in-flight capture, dropped network connection, corrupt lease state and a complete takeover-and-return cycle. The author reports finding and correcting failures in these cases during review. Those reports are useful engineering evidence, not tests reproduced here. Before adopting a future release, confirm which desktop path actually landed and whether it isolates only the display or also the operating-system identity.

Caveat

Open proposal with author-reported Linux/Desktop demonstrations. Per-profile Xfce sessions still run under one OS user, so this is not a tenant-isolation guarantee. Realms remains a separate draft with dependencies and gated hosted CI; neither its tests nor Bot Screen's tests certify the other implementation.