Hermes Workspace

Hermes Workspace is a self-hosted command center for the Hermes autonomous AI agent, providing a unified interface to orchestrate agents, browse memory,…

  • AI
  • Automation
Hermes Workspace is a self-hosted command center for the Hermes autonomous AI agent, providing a unified interface to orchestrate agents, browse memory, manage skills, run scheduled jobs, and access a terminal. It is not a chat wrapper but a full operations workspace for managing a running Hermes Agent deployment, suitable for homelab users who want centralized control over agent infrastructure.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
75last commit 91 days ago
Popular
776,822 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
108 GB minimum RAM
Security check
76no serious findings, 4 minor, CI, tests

Availability: platform listings confirmed today, links checked 21 days ago

GitHub stars
6,822
Open issues
191
Last commit
2026-08-22
Latest release
v2.3.0
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (outsourc-e/hermes-workspace)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 500 MB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check Hermes works before moving on Run `hermes doctor` and then `hermes chat -q "Hello"` after installing. This checks that the `hermes` command is found in your PATH (the list of places your terminal looks for commands) and basic chat works, so you know the install is healthy before adding API keys or other setup. source
  • Keep your .hermes folder safe Keep this folder safe: the standard installer puts Hermes under `~/.hermes` by default (the home folder for your user, usually `/home/username`). If you delete or move it, you can lose the installed app and settings, and later commands may fail. source
  • Test plugins before enabling them For optional plugins (add-ons that extend Hermes), use `hermes plugins install owner/repository --no-enable`, then `hermes plugins list`, and only enable the plugin you want. This stops a bad or unexpected plugin from loading at startup and causing errors or changed behavior. source
  • Unraid user mapping In the Unraid template, add "--user 99:100" to Extra Parameters so the container runs with the correct filesystem permissions for the /hermes share. source
  • Template configuration reference For the full list of environment variables and compose settings, see the docker-compose.yml and .env.example files in the Hermes Workspace GitHub repository. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where does the standard Hermes installer store local state?

It uses the user's .hermes folder, defaulting to ~/.hermes. Keep that folder safe because deleting or moving it can lose the installed app and settings.

What commands verify a new Hermes install before adding API keys?

Run hermes doctor and then hermes chat -q "Hello". This checks that the hermes command is on PATH and basic chat works.

How should optional Hermes plugins be installed safely?

Install with --no-enable, list the plugins, and enable only the intended plugin. This prevents a bad plugin from loading at startup.

Which port conflict is reported when self-hosting Hermes?

A port 18790 conflict is one of the real self-hosting errors reported.

What Node issue can break a self-hosted Hermes setup?

A Node version mismatch is listed among real self-hosting errors.

Does Hermes Workspace require a fork of Hermes Agent?

No. Hermes Workspace v2 is zero-fork and runs with vanilla Hermes Agent installed via Nous's own installer.

Answers sourced from github.com, hermes-agent.nousresearch.com, hermes-agent.nousresearch.com, hermesinstall.com

Community

Collected 49 days ago - public community threads