[Feature]: Desktop Client-Only Installation

[diegohb]

Problem or Use Case

Install Hermes Desktop as thin-client connecting to remote hermes installation.

---

The Reality

The desktop app is designed to always bootstrap the Hermes Agent runtime on first launch if no installation is found. 2 The bootstrap runner in electron/main.cjs automatically runs install.ps1 stages to install Python, Node, and other dependencies. 3

Remote Mode Workaround

If you set these environment variables before first launch, the desktop app will connect to a remote backend and skip the local backend spawn:

HERMES_DESKTOP_REMOTE_URL=https://your-remote-backend.com/hermes
HERMES_DESKTOP_REMOTE_TOKEN=your-session-token

When these are set, resolveRemoteBackend() returns a remote configuration and startHermes() connects to it immediately, never reaching the local backend code path. 4 1

Limitations

• The Electron shell itself is still installed (that's the desktop app)
• If you ever unset the environment variables, the app will attempt to bootstrap the local runtime on next launch
• There's no official "client-only" build that excludes the bootstrap logic entirely

Notes

The bootstrap logic is in ensureRuntime() which only runs when backend.kind === 'bootstrap-needed' — meaning no usable local installation was found. 3 Remote mode via environment variables is the intended way to use the desktop app without a local backend, but it doesn't prevent the initial bootstrap attempt if the env vars aren't set before first launch.

Proposed Solution

Flag for installer that doesn't install or run server components.

Alternatives Considered

No response

Feature Type

Other

Scope

Small (single file, < 50 lines)

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)

[bbhenry]

This would be nice. I just want to connect Hermes desktop app to my existing remote hermes agent without a local installation.

[warezio]

I have the same use case and would really like this to be supported as a first-class Desktop flow.

My setup / desired workflow:

• Run the actual Hermes runtime/gateway on a remote machine that is always on.
• Install only the macOS Hermes Desktop app on my Mac as a client.
• Connect Desktop to the remote gateway/backend over a private network such as Tailscale.
• Avoid installing or bootstrapping a local Hermes CLI/runtime/gateway on the Mac.
• Avoid duplicate local config, providers, skills, memory, or accidental local backend startup.

Current pain point:

• The macOS Desktop app still feels local-first: first launch pushes the user toward "Install Hermes" / local bootstrap.
• Even when the goal is remote-only, it is not obvious that Desktop can be used purely as a remote client.
• If Desktop restarts or reconnects, it is easy to worry that it may try to set up or start a local backend again instead of staying in remote-client mode.

What would solve it for me:

• A visible startup option like "Connect to existing Hermes" / "Remote client only".
• Remote URL + token setup in the Desktop UI.
• A Desktop-only macOS install path that does not install or start a local Hermes runtime.
• Clear indication in the UI that the active backend is remote, including what machine file/terminal/tool execution targets.

In short: I want Hermes Desktop for macOS to behave like a thin client for an existing remote Hermes Agent, without requiring a local Hermes installation.

[aptonline]

I came to raise the same issue as have the exact same use case. Seems a waste of resources to install everything if all you want to do is connect to a remote instance. Back this 100%.

[StarrWulfe]

+1 for a local install of the desktop UI Only to have it connect with an already existing local/LAN/WAN/Cloud instance of Hernes.
+2 if Flatpak.
+3 if Nix.

[k7cfo]

Very much agree with @warezio - I don't want to run hermes local on my desktop, the installer should allow for a nice desktop experience and connect to a remotes hermes install with as little blast radius as possible.

[vmhq]

A client-only mode would be ideal for those of us running Hermes Agent remotely on another machine. Right now the Desktop binary bootstraps a full local runtime on first launch, which is unnecessary when you already have a Hermes instance running elsewhere.

[cogitech2]

I vote for this one, too. Please, please, please!