Roamgate's SSH connections require a Herdr server already running on each agent host. It forwards that host's control and terminal sockets; Herdr owns the panes where agents run. In this browser setup, remote Herdr installation/startup is a separate deployment step.

What runs on the central server and agent hosts?

For the browser setup discussed here, process ownership is:

Location	Running components
Your device	Browser frontend
Central host	Roamgate web bridge and outgoing SSH connections
Each agent host	Herdr background server, terminal panes and agent processes

Roamgate's deployment documentation requires an already-running remote Herdr server. Its managed Herdr setup helper supports the default local configuration only. Deploy and start Herdr separately on remote hosts.

The SSH transport forwards two remote sockets: the control API and terminal traffic. The central bridge connects to those existing services. Reconnecting to a host does not itself mean launching a new agent for each message.

Agent launch is a separate operation inside a Herdr pane. The automation guide provides agent start for an existing shell pane and identifies OMP, Codex and other executables as supported kinds. The agent runs on that host and uses its filesystem and environment.

This describes documented operation, not a deployment performed here.