Connect a Linux runtime host using the one-time command shown by EmperorClaw, inspect its capacity and provider availability, then hire an authorized Hermes worker onto it. Verify a direct-message round trip before assigning work. Remote host management uses fixed audited commands, not an arbitrary remote shell.
Choose where the work should run
A control panel and an agent runtime have different jobs. EmperorClaw stores the company work record; Hermes executes turns and tools on its host. You may keep them together for a small installation or connect another Linux machine for separate capacity.
Choose based on the task’s tools, available memory, uptime and source access. A machine that can run a lightweight text worker may not have the browser or capacity needed for a larger assignment. Shared gateways can reduce overhead but couple restart behavior.
Pair the host through Settings
Owners and admins open Settings → Runtime hosts → Connect a host. Use the current command shown there on the machine as the user that will run the agents. The one-use code pairs the host service with this Emperor installation.
The host connection has its own key, separate from agent tokens. Use the documented HTTPS connection path. Do not paste credentials into a task or public chat to make pairing easier. Consult the runtime manual if the host has an older daemon or unsupported setup.
Review what the machine reports
The host card exposes capacity information, versions, browser availability and model provider names. Provider API keys stay on the machine; names reported to the dashboard are not secret values.
A host must be connected and eligible before it can be selected for hiring. If the provider key is missing or the host lacks memory, resolve that prerequisite rather than repeatedly creating failed workers. Give the host access only to external systems its assigned work requires.
Hire and verify one worker
- Choose a Hermes role and the connected machine in the hire flow.
- Select an available provider and model.
- Set who may use the worker and its intended data scope.
- Watch provisioning until it is online, or inspect the named failure.
- Send a private test message and verify the correct identity replies.
- Assign a harmless task and inspect the run and output.
Failed setup has Retry and removal paths. Do not create lookalike agents to work around a failed identity or connection check. OpenClaw uses its own integration; this managed remote provisioning flow is for Hermes.
Know the impact of a restart
Authorized admins can request bridge or gateway restarts and watch progress. On a shared gateway, restarting it affects multiple agents. Review the idle-wait option and warnings before choosing an immediate restart.
These commands are fixed and audited. Connecting a runtime host does not grant a general-purpose shell through Emperor. If a task needs shell access, that belongs to the runtime’s tool and permission configuration, not the host-management channel.
Remove and revoke with the offline case in mind
Deleting a remote agent can also remove its profile from the connected machine. Its Emperor access is revoked immediately, while host cleanup may wait if the machine is offline. Inspect pending removals rather than assuming a remote filesystem has already changed.
Host revocation cuts off its management connection. It is distinct from removing an agent profile or rotating an external provider key. Keep those actions separate in your operating checklist.
Use the versioned runtime instructions
The Hermes runtime manual covers installation, topology, pairing, logs and recovery. Use commands generated by your installed Emperor version rather than copying an old pairing code from an article. Pair this setup with a recovery exercise.