Should I run the one-line installer from a random blog?
No. Use this page to understand the path, but copy the final command from the official installation guide or official repository.
Install path chooser
Start with the supported installer for your operating system, then verify a first session before adding providers, gateways, skills, or sensitive files.
Agent Guide is an independent editorial resource. It is not affiliated with, endorsed by, or sponsored by Nous Research, Hermes Agent, or Hermes/Hermes brand owners. Product names and marks belong to their respective owners.
| Environment | Recommended first path | Why |
|---|---|---|
| macOS or Linux | Official one-line installer | Shortest route to a normal local setup. |
| Windows and comfortable with WSL2 | Linux installer inside WSL2 | Most battle-tested Windows route in current docs. |
| Windows and avoiding WSL2 | Native PowerShell installer | Useful, but treat as early-beta and verify more carefully. |
| Self-hosted or safety-first | Docker | Cleaner data volume and stronger deployment boundary. |
Run only the command that matches your environment. After installation, open a new terminal and verify that the hermes command is available before connecting providers or gateways.
# Linux / macOS / WSL2
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash
# Native Windows PowerShell
iex (irm https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.ps1)
hermes --help prints CLI help.| Symptom | Likely cause | Next check |
|---|---|---|
| Command not found | Terminal PATH not refreshed | Open a new shell and inspect installer output. |
| Windows shell tooling missing | Native Windows support or Git Bash dependency issue | Compare native Windows with WSL2 route. |
| Provider setup stalls | Missing API key or wrong provider selection | Use the providers guide before retrying. |
| File access feels too broad | Local backend runs as your user | Read the security guide before continuing. |
| User intent | Best first page | Success signal |
|---|---|---|
| I am on macOS | Install Hermes Agent on macOS | hermes launches after a new shell picks up PATH. |
| I am on Linux or WSL2 | Install Hermes Agent on Linux | hermes doctor reports the expected install layout. |
| I want isolation or a VPS | Docker or Docker Compose | Container starts with a dedicated /opt/data mount. |
| I am on native Windows | Hermes Agent on Windows | PowerShell install finishes and Git Bash dependencies are available. |
| I am not sure the repo is real | Hermes Agent GitHub source review | You can identify the official repo, releases, issues, and install scripts. |
hermes --help or hermes should start without a command-not-found error.hermes model or setup flow should be reachable before provider keys are added.hermes doctor should give actionable diagnostics if dependencies are missing.| Source | Used for | Last checked | Confidence |
|---|---|---|---|
| Hermes Agent installation guide | Install commands, prerequisites, Windows/native installer details, and post-install checks. | 2026-06-02 | high |
| Hermes Agent configuration guide | Provider, model, backend, and environment configuration patterns. | 2026-06-02 | high |
| Hermes Agent Docker guide | Docker run modes, mounted data directory, gateway operation, ports, and production cautions. | 2026-06-02 | high |
Known caveats: The official installer details can change. Confirm the command in the official installation guide before running it on a machine with important credentials.
No. Use this page to understand the path, but copy the final command from the official installation guide or official repository.
Use Docker first when isolation, repeatability, or VPS operation matters more than local desktop convenience.
Operator checklist
Receive the smoke-test order for install path, sandbox boundary, provider setup, source review, and production checks.