Hermes Agent Zone

Guides

How to install Hermes Agent on Windows

Published August 5, 2026 · Verified on v0.19.0

Windows has two genuinely supported paths, and picking the wrong one costs you later. The install itself is one line either way.

Which one should you use?

Native WindowsWSL2
Setup effortOne commandInstall WSL first, then one command
Matches community guidesRarelyAlmost always
Filesystem pathsC:\Users\…Unix paths
Finding help when stuckHarderEasy

Pick native if you want to try Hermes in the next five minutes and you do not already use WSL.

Pick WSL2 if you expect to run this seriously. Nearly every guide, GitHub issue and forum answer assumes a Unix-shaped system. On native Windows you will hit moments where the advice you find simply does not map.

Native Windows install

Open Windows PowerShell — your normal user, not an administrator prompt:

iex (irm https://hermes-agent.nousresearch.com/install.ps1)

That downloads and runs the official installer script. If you would rather read it before executing it, which is a reasonable habit:

irm https://hermes-agent.nousresearch.com/install.ps1 -OutFile hermes-install.ps1
notepad hermes-install.ps1
.\hermes-install.ps1

If PowerShell refuses to run the saved file, execution policy is blocking it. Scope the change to the current session only rather than loosening it permanently:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

That reverts the moment you close the window.

Open a new terminal

The installer updates PATH, and PowerShell reads PATH when the session starts. Your existing window will not see it. Close it, open a fresh PowerShell, then:

hermes doctor

If Defender or SmartScreen interrupts

An unsigned script that downloads runtimes looks exactly like what security tooling is built to flag. That is the tooling working, not evidence of a problem. Confirm you fetched the URL from the official documentation, and if your organisation manages the machine, ask them rather than disabling protection yourself.

WSL2 install

If WSL is not set up yet, in PowerShell as administrator:

wsl --install

Reboot when it asks. After that you have an Ubuntu shell — from there Hermes installs exactly as on Linux:

sudo apt update && sudo apt install -y git curl xz-utils
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
source ~/.bashrc
hermes doctor

Then follow the Linux guide for the rest, including running it as a service.

Keep your files inside WSL. Working in /home/you/ is dramatically faster than /mnt/c/Users/you/, where every file operation crosses a translation layer. For an agent that reads and writes constantly, the difference is not subtle.

Configure it

Either path, same commands:

hermes model     # choose your LLM provider
hermes           # start chatting

An HTTP 400 on the first message is a model identifier your provider does not recognise, not a bad key — confirm it in one command.

For the full wizard:

hermes setup

Keeping it running

Neither Windows path gives you the clean always-on story that systemd does on Linux. WSL2 shuts its VM down when idle, and a desktop that sleeps is not answering messages.

For interactive use this does not matter. For an agent expected to respond unprompted, put it on a small always-on box and keep Windows as your client.

Upgrading

Hermes releases most weeks. Read the changelog for breaking changes before upgrading, and re-run hermes doctor afterwards.

FAQ

Should I use native Windows or WSL2?

Native is simpler to start and fine for interactive use. WSL2 matches what nearly every guide, issue thread and troubleshooting answer assumes, so when something breaks you will find answers that apply. If you already use WSL, stay there.

Do I need to run PowerShell as administrator?

No, and you should not. Hermes installs per-user. Elevating changes where files land and can leave you with an install your normal session cannot use.

Why does the hermes command not work after installing?

PowerShell reads PATH when the session starts, so a terminal opened before the install will not see the new entry. Close it and open a new one.

Can I run Hermes Agent on Windows Server?

The native installer targets desktop Windows. For a server that needs to stay up, a small Linux box is the better-trodden path and is what the systemd instructions in the Linux guide assume.

Related