Can native Windows and WSL2 coexist?
The official installation docs say native and WSL2 installs can coexist cleanly because their data directories differ.
Native vs WSL2 vs Docker
Hermes Agent on Windows
Use WSL2 when you want the most battle-tested path. Use native Windows when you specifically need a Windows-native setup and can tolerate early-beta rough edges. Use Docker when deployment isolation matters more than direct desktop convenience.
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.
Decision matrix
| Path | Best for | Trade-off |
|---|---|---|
| WSL2 | Most Linux-like Hermes experience | Requires WSL setup and Linux filesystem habits. |
| Native Windows | Users avoiding WSL2 or Docker | Treat as early beta and verify shell/browser behavior. |
| Docker | Cleaner service-style operation | Needs Docker Desktop and volume/network understanding. |
Native Windows checks
- Run PowerShell as a normal user unless the official docs require otherwise.
- Confirm
hermes --helpworks in a new shell. - Check that Git Bash or the bundled shell dependency is available for terminal-tool behavior.
- Avoid connecting credentials until a simple non-sensitive task succeeds.
Troubleshooting pattern
- Capture the exact command and shell where the failure happens.
- Check whether the same command works inside WSL2.
- If terminal-tool behavior differs, test Docker before modifying production files.
- Document the environment in the page update notes if the failure becomes repeatable.
Windows success criteria
- PowerShell install completes without requiring administrator rights unless your environment policy requires it.
- A new shell can find
hermesfrom User PATH. - PortableGit or an existing Git install is available for shell-dependent behavior.
- You understand that the dashboard chat terminal pane is the main WSL2-only feature called out in official docs.
When to switch paths
| Symptom | Switch to | Why |
|---|---|---|
| Native terminal behavior differs from docs | WSL2 | It gives a Linux-like shell and file layout. |
| You need a stable service boundary | Docker | Container state and mounts are easier to isolate. |
| You only need desktop convenience | Native Windows or desktop installer | The official installer handles Python, Node, Git Bash, ripgrep, and ffmpeg. |
| You need to debug scripts deeply | WSL2 or Linux | Most shell examples and issue reports are easier to compare there. |
Official sources reviewed
| 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 |
| NousResearch/hermes-agent on GitHub | Repository discovery, release/source inspection, issues, and contribution context. | 2026-06-02 | high |
Known caveats: Hermes Agent is moving quickly. Treat commands and support status as current only as of the verification date, then check the official docs before changing production systems.
FAQ
What should I capture in a Windows bug report?
Capture shell type, command, sanitized output, whether Git Bash is present, and whether the same command works in WSL2.
Operator checklist
Get the Agent Guide launch checklist
Receive the smoke-test order for install path, sandbox boundary, provider setup, source review, and production checks.