Own Compute
From its catalog listing
Bring your own compute. For researchers and scientists with a workstation, a lab server or a cluster account. Runs sandboxed container environments, Slurm batch jobs and cloud agents (a Hermes agent in a sandbox on the user's own machine, not a hosted service, that hands its work back as a git branch) on SSH hosts, Slurm login nodes, and the Docker or Podman on this computer. Independent of Nous Research. A Compute page in Hermes Desktop shows every machine and what runs on it, and the same actions are chat tools with approval cards before anything starts, changes or is deleted.
Good to know before installing
runs ssh, git and the container runtime (podman or docker), and on Slurm hosts sbatch, squeue, sacct, scancel and srun, on the hosts you add; opens ssh -L tunnels bound to 127.0.0.1 and terminal windows when you click; adds a host's key to your SSH known-hosts file on first contact (accept-new); remote hosts pull container images from public registries; cloud agents send the model key you store as a Hermes secret (CC_AGENT_API_KEY or a profile model's key) into the agent's sandbox, where commands the agent runs can read it, and call the model endpoint you choose from inside that sandbox only; one background thread starts on the first tool call or chat turn (reachability checks, Slurm and agent polling, time and idle limits); stores hosts, templates, run records and saved file copies in the plugin's data folder; reads secrets only through the Hermes secret scope; no telemetry, no update check, no call to any service run by the author.
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 own-compute - Said no? Turn it on later:
hermes plugins enable own-compute - 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
- Chat apps & voice · Web, research & browsing
- Maintained by
- Siioh (Community)
- Needs
- No API keys declared
- Adds tools
compute_statusenv_spawnenv_execenv_controlenv_openslurm_submitslurm_jobscloud_agent_spawncloud_agent_statuscloud_agent_collectcloud_agent_stopenv_filescompute_hostcloud_agent_messagecloud_agent_rerun- Adds hooks
pre_llm_callpre_tool_call- Works on
- linux, macos, windows
- Needs Hermes
- 0.23.0 or newer
- Version
- 0.1.0
- In the catalog
- 2026-11-15
Known issues (from its catalog listing)
- Tested on Windows 11 (Hermes Webapp), Fedora 43 with rootless Podman, and macOS 27.2 on Apple Silicon, against a Slurm test cluster running in containers. The native Hermes Desktop app, GPUs and Docker on Linux were not tested.
- Cloud agents need a model from an API-key provider or a model server you run; a sign-in or subscription provider cannot be used. The agent's key is readable by commands the agent itself runs in its sandbox: use a scoped, spend-capped key.
- Slurm only (no PBS or LSF). Cloud agents are off on Slurm hosts. The Hermes gateway has to run on the computer that shows the Compute page. An EC2 host starts a machine in your own AWS account that AWS bills while it runs; EC2 was tested on us-east-1 and t3.micro only.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in chat apps & voice
New Hermes Agent updates every day on X. Follow @HermesWatcher