Technical Research · July 10, 2026

Hermes Agent As A Remote-PC Workspace

Can the desktop app run locally while the agent, files, commands, sessions, and work remain on another PC?

VERDICT: YES

Hermes Desktop officially supports this exact arrangement. Run hermes serve on the remote PC, then set the local app’s Settings → Gateway → Remote gateway URL to that remote backend. Your typing and rendering happen locally; Hermes tool execution and state live on the remote machine.

Adam’s Tailscale Architecture

LOCAL CLIENT · MACBOOK

adamobook

Hermes Desktop app
Local keyboard input
Local UI rendering
Remote sessions and previews

TAILSCALE TAILNET

Authenticated private path
WebSocket + Hermes auth
TCP 9119

REMOTE HOST · MAC MINI

forgebot-mini

hermes serve
Agent runtime and sessions
Files, repositories, and tools
Model credentials and memory

Connection target: Hermes Desktop on adamobook uses Settings → Gateway → Remote gateway to connect to http://forgebot-mini:9119 through Tailscale MagicDNS, or to the Mac Mini’s stable Tailscale IP if MagicDNS is unavailable.

This is not screen sharing. The local app sends structured chat/WebSocket traffic, so it avoids the high-latency keystroke/desktop-image loop that makes AnyDesk-style input feel sluggish. Network latency still affects response streaming and tool updates, but not the tactile act of typing.

RECOMMENDED

Remote Hermes Backend

Hermes itself runs on the remote PC. The local desktop app is a thin authenticated client. Best when the remote PC owns the repository, credentials, local apps, memory, sessions, and background work.

Local Hermes + SSH Backend

Hermes runs on the main PC, but terminal/file/code tools are routed through SSH. Useful for a remote server shell; less faithful when you want the complete remote Hermes environment, desktop-specific apps, or all remote state.

Browser Dashboard

A browser can manage a remote Hermes installation and inspect sessions/configuration. It is a reasonable fallback, though the native desktop remote-backend mode is the cleaner day-to-day chat surface.

What You Will And Will Not See

Capability	Result
Type locally with responsive keyboard input	Yes. Text entry occurs in Hermes Desktop on `adamobook`.
See Hermes replies, tool calls, streaming progress, and remote sessions	Yes. Desktop attaches to `hermes serve` on `forgebot-mini`.
Operate on the Mac Mini’s files and command environment	Yes, because the agent backend and tools run there.
See the remote macOS desktop pixel-for-pixel	No. This is an agent UI, not a general remote-display protocol.
Directly manipulate arbitrary remote GUI applications	Only if Hermes has an appropriate computer/browser-control tool configured. For ordinary GUI work you still need Screen Sharing or a purpose-built interface.
Continue if `hermes serve` stops	No. The remote service must remain running and reachable.

Safe Setup Path

Install/update Hermes Agent on forgebot-mini and run its setup/doctor flow.
Confirm adamobook and forgebot-mini are signed into the same Tailscale tailnet. Do not expose port 9119 publicly.
Configure Hermes username/password authentication with a stable signing secret as defense in depth.
Start hermes serve on forgebot-mini, bound to its Tailscale IP and port 9119. After validation, keep it alive with a macOS LaunchAgent or LaunchDaemon.
Install Hermes Desktop on adamobook. In Settings → Gateway → Remote gateway, enter http://forgebot-mini:9119, sign in, then Save and reconnect.
Run a harmless proof: ask Hermes for hostname, current directory, and a directory listing. Confirm the hostname is forgebot-mini.
Test resume/reconnect after restarting both Macs before relying on it unattended.

Security boundary: forgebot-mini can expose Hermes secrets and command execution through this service. Keep it private to the Tailscale tailnet, retain Hermes authentication, and do not use Tailscale Funnel or router port forwarding for port 9119.

Important Nuances

The docs distinguish hermes serve (Desktop’s backend) from hermes gateway (Telegram/Slack/etc.). You need serve for Desktop; messaging requires its own process.
The remote host is configured per Hermes profile, so one profile can target the remote PC while another stays local.
A stable auth signing secret prevents being logged out whenever the backend restarts.
Hermes also supports an SSH terminal backend. That moves command execution remotely but does not relocate the whole agent runtime/session store in the same way.
On this main PC, the hermes command was not found on PATH during this review; installation/configuration remains to be done.

Sources

Official Hermes Desktop documentation — remote backend architecture and setup.
Official Web Dashboard documentation — authentication, remote connections, sessions, and security.
Official Tools & Toolsets documentation — SSH and other execution backends.
Official Configuration documentation — terminal/backend behavior.
Official GitHub repository — implementation and project activity.

External evidence: current official Nous Research documentation and repository. Internal evidence: ForgeApps Hermes operating guide. Confidence: high for the Tailscale remote-backend architecture; the exact macOS LaunchAgent or LaunchDaemon definition should be validated against the installed Hermes binary path on forgebot-mini.