Blog / installation

How to Install Hermes Agent on Windows 11 (Native and WSL2)

Windows is a legitimate Hermes Agent host, but it is not the platform the project's install instructions were written for first. This guide covers the two working paths on Windows 11, how to verify the install, and the point at which a local install stops being the cheap option.

Updated Sep 10, 202610 min read
Deployment route
  1. 01

    Pick the install path

    Use WSL2 when you want the Linux behaviour the documentation assumes, and the native Windows path when you need the agent inside your existing Windows environment.

  2. 02

    Prepare the environment

    Install the runtime prerequisites, then confirm the shell can reach the package source before you start the agent install.

  3. 03

    Install and start the gateway

    Run the installer, start Hermes Agent, and confirm the gateway is listening locally before you add any channel.

  4. 04

    Verify with one real message

    Connect a single test channel and send one message to prove the full path from channel to model and back.

Four-step path

How do you install Hermes Agent on Windows 11?

Choose WSL2 unless you have a specific reason to run native, then verify the gateway before connecting a messaging channel.

  1. Step 01

    Pick the install path

    Use WSL2 when you want the Linux behaviour the documentation assumes, and the native Windows path when you need the agent inside your existing Windows environment.

  2. Step 02

    Prepare the environment

    Install the runtime prerequisites, then confirm the shell can reach the package source before you start the agent install.

  3. Step 03

    Install and start the gateway

    Run the installer, start Hermes Agent, and confirm the gateway is listening locally before you add any channel.

  4. Step 04

    Verify with one real message

    Connect a single test channel and send one message to prove the full path from channel to model and back.

Should you use WSL2 or the native Windows path?

Choose WSL2 if you want the closest match to the documented Linux experience, and the native path if you need the agent to live inside your normal Windows shell and toolchain.

  • WSL2 follows the Linux instructions closely, so fewer steps differ from the documentation.
  • WSL2 keeps the agent isolated from your Windows user profile.
  • The native path keeps the agent next to your Windows tooling and files.
  • Either path works with the same model providers and messaging channels.
  • Pick one and stay on it, because mixing environments is the most common source of confusing failures.

How do you verify the install actually works?

Verification is not 'the installer finished'. Start the agent, confirm the gateway is listening, confirm the model provider responds, and only then connect a channel.

Test in that order. If the channel does not answer, you then know whether the fault is in the agent runtime or in the channel credentials, which is the difference between a five-minute fix and an afternoon of guessing.

What breaks on a local Windows install?

The common failures are an environment mismatch, a gateway that is not listening, missing channel permissions, or a model key without quota. None of them are Windows-specific, but all of them are easier to hit when the platform differs from the documentation.

Sleep and restart behaviour is the other difference worth knowing about. A laptop that suspends overnight will stop answering, which is fine for experimentation and unacceptable for a team channel.

When is a managed deployment the better answer?

Move to a managed deployment when the agent needs to be available when your laptop is closed, when more than one person depends on it, or when nobody wants to own updates and restarts.

A local install is the right way to evaluate Hermes Agent. It is the wrong way to run a channel other people rely on, because the runtime inherits every limitation of the machine it sits on.

Which primary sources support this page?

Product behavior is checked against the current deployment flow. These external links provide the upstream project or channel documentation used for setup details.

Direct answers

Frequently asked questions

Does Hermes Agent run on Windows?

Yes. Hermes Agent runs on Windows 11 both through WSL2 and through a native Windows path, with the Linux documentation being the closest reference for WSL2.

Do I need WSL2 to install Hermes Agent on Windows?

No, but WSL2 follows the documented Linux workflow most closely and avoids environment mismatches, which makes it the safer default for a first install.

Why does my agent stop answering overnight?

A laptop that sleeps stops running the gateway. Keep the machine awake for always-on use, or move the agent to a host that stays up.

Can I move a local install to a managed deployment later?

Yes. Instructions, skills, and channel credentials can be re-created in the managed deployment, which is normally a short piece of work.

Do I need a server to use Hermes Agent?

Not to evaluate it. For a shared or always-on assistant, a persistent host or a managed deployment is the practical choice.

Key takeaways

  • Windows is a legitimate Hermes Agent host, but it is not the platform the project's install instructions were written for first. This guide covers the two working paths on Windows 11, how to verify the install, and the point at which a local install stops being the cheap option.
  • Start with one model, one channel, and one controlled test conversation.
  • Use managed hosting when deployment speed matters more than operating the server yourself.

Put Hermes Agent in the channel where the work already happens.