Draw the boundaries first
Hermes supports several host platforms and terminal backends. The machine running the agent and the environment executing its terminal commands can be different. A remote execution backend does not by itself move every configuration file, memory entry or scheduled service off your laptop.
Sketch four locations: the Hermes process, the command environment, the source data and the final artifact. Add the network paths and accounts connecting them. This exposes assumptions such as a server task needing a file that exists only in your Downloads folder. It also makes storage planning much more realistic than estimating the size of application code alone.
Choose using operating needs
A personal machine is convenient for development and access to local files. An always-available host can suit recurring work, provided its processes, credentials and persistent storage are managed. Container or remote execution can provide a separate command environment, but requires explicit decisions about mounts, networking and retained data.
Before migration, run a small task that writes a disposable artifact, reconnect and read it back. Check which settings and secrets the service actually receives. Define backup scope, retention and recovery before growing a large collection of logs or media. Test one restart and confirm the expected work can resume without relying on an interactive terminal left open.
Scope and limits
The current platform matrix includes native Windows as well as Linux, WSL2 and macOS, with distribution-specific restrictions. Consult that matrix for the chosen architecture and installation method. This guide does not estimate hosting costs or certify a deployment. A supported platform still needs task-specific validation, and a cloud workspace may have separate persistence and billing rules.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.
New Hermes Agent updates every day on X. Follow @HermesWatcher