Local Hands
From its catalog listing
Remote brain, local hands: Hermes runs on your server while terminal, read_file, write_file, patch, search_files and execute_code run on your own computers, through a one-file, stdlib-only daemon that dials out to the Hermes host over key-pinned TLS and asks you before acting (per conversation, per command, or never). Pair several machines and let the agent switch between them and the host with the hands tool; each keeps its own working directory. Answers #18715 and #1855 on the public terminal-backend surface.
Good to know before installing
starts a long-running detached hub process on the Hermes host that listens on all network interfaces on a TCP port (default 0.0.0.0:7717, self-signed TLS, so clients use ssl.CERT_NONE plus a SHA-256 public-key pin) once the hands backend runs its first command or you run `hermes hands up` / `pair`, and serves the daemon source hands.py over HTTPS on that port (no self-update); runs shell commands sent by the Hermes host on each paired machine under the user's account (not a sandbox); with the 'brain' target on (the default) the agent can also switch its terminal to the Hermes host itself, through Hermes' local backend; command output returns to Hermes and so to the model provider; writes TLS key and certificate, devices.json (token hashes only), audit.jsonl and hub.log under plugin-data/local-hands/, and ~/.config/local-hands/ on each machine; adds one short context line to a turn when the active machine changes; Hermes dangerous-command approvals stay on; no telemetry, no third-party service, no credentials read from files.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install local-hands - Said no? Turn it on later:
hermes plugins enable local-hands - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Web, research & browsing · Automation & multi-agent
- Maintained by
- noegng (Community)
- Needs
- No API keys declared
- Adds tools
hands- Adds hooks
pre_llm_call- Works on
- linux, macos
- Needs Hermes
- 0.22.5 or newer
- Version
- 1.1.0
- In the catalog
- 2026-11-15
Known issues (from its catalog listing)
- The hands daemon runs on macOS, Linux and WSL (bash and Python 3.8+); not on native Windows.
- The active machine is chosen per conversation (each gateway chat keeps its own; the CLI is one conversation) and is kept in memory: a chat returns to the default machine when Hermes restarts.
- Hermes and its hub talk through a Unix socket: where the operating system forbids those (some sandboxes and seccomp profiles) no machine can be reached, and the hands tool, hermes hands doctor and the command output say so.
- Environment variables and skill files are not sent to the machine; browser and computer_use tools still act where Hermes runs.
- After a cd, Hermes may resolve relative write_file/patch paths against the machine's workspace rather than the new directory; absolute paths are exact.
- Needs plugins.isolation in_process (the default): Hermes cannot hand a terminal environment across the plugin-host boundary.
- Imports tools.environments.base (BaseEnvironment, EnvironmentConnectionError), the base class every terminal backend subclasses, tools.environments.local (LocalEnvironment), which runs commands sent to the 'brain' target with core's credential-stripped environment, and hermes_cli.plugin_session (session_key), which tells which conversation a hands tool call belongs to (guarded: without it the active machine is process-wide, as in 1.0.0); hermes plugins validate reports the three as private-import warnings.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in web, research & browsing
All web, research & browsing plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher