Hermes Teleoperator
From its catalog listing
Keep one conversation on the gateway while switching shell, files, skills and explicitly permitted MCP tools between machines over SSH. The standalone Rust receiver needs no Hermes or language runtime. Commands have the destination SSH user's full OS authority; this is not a sandbox.
Good to know before installing
Routes this conversation's terminal, file, process, skill and allowlisted MCP tool calls to SSH machines you configure, where the author's Rust receiver runs them with that SSH user's full authority; Hermes' dangerous-command and human-approval prompts run before each routed call, but other plugins' pre_tool_call blocks and the agent's tool guardrails do not see routed calls until core adds a seam (hermes-agent#152963). The optional `python -m hermes_teleoperator.deploy` helper downloads the receiver from the author's GitHub release (SHA256 pinned in the plugin source, build-attested) and installs it on the remote host over SSH; file transfers need approval, and gateway-local transfers stay inside a configured transfer_dir.
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 hermes-teleoperator - Said no? Turn it on later:
hermes plugins enable hermes-teleoperator - 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
- Security & privacy
- Maintained by
- Tsurgcom (Community)
- Needs
- No API keys declared
- Adds tools
teleoperator- Adds hooks
pre_llm_callon_session_end- Works on
- linux
- Needs Hermes
- 0.21.3 or newer
- Version
- 1.2.0
- In the catalog
- 2026-11-15
Known issues (from its catalog listing)
- Windows is unsupported. Linux is the only catalog-claimed platform; macOS binaries exist but are not execution-tested in CI.
- Gateway and receiver versions must match exactly. SSH keys and verified known-host entries must already be configured.
- Receiver runs with the SSH user's authority. Gateway applies Hermes' dangerous-command and human-approval gates before routing, but other plugins' pre_tool_call hooks and the agent's tool guardrails cannot see routed calls until Hermes provides a pre-execution seam (hermes-agent#152963). Browser, memory, cron and delegation do not migrate.
- Remote MCP is explicit-allowlist stdio only; sampling, elicitation and interactive callbacks are rejected. Remote content search is blocked; filename search remains available. Small-file transfers are limited to 8 MiB.
- Transfers require human approval scoped to the exact source, destination and move setting. Gateway-local transfers require a configured transfer_dir; deleting a gateway-local source additionally requires allow_local_delete: true.
- Receiver downloads are verified against per-asset SHA256 digests committed in the plugin source for the exact release tag; SHA256SUMS is cross-checked but is not the trust root. Release assets carry GitHub build-provenance attestations. SSH key authorization remains a manual administrator action.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in security & privacy
All security & privacy plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher