· Updated · 8 min read · Omkar Satpute and Milind Soni

Hermes Agent on Windows: native install, and a GUI for it

Hermes Agent is Tier 1 on Windows 10 and 11: one PowerShell line, no WSL. The current install, what still breaks, and how to run Hermes inside MausBot.

Yes, Hermes Agent runs natively on Windows 10 and 11. It is a Tier 1 platform, the install is one PowerShell line, and you do not need WSL. What still breaks, or broke recently: a first-run dependency install failure that is still open, an update that once deleted the gateway service, and a PATH that only shows up in a new terminal. The always-on gateway is a Scheduled Task, not a Windows Service. If you want a desktop chat app around Hermes rather than a terminal or a Telegram bot, MausBot runs Hermes as one of its 16 agent engines on Windows, next to Claude Code, Codex, and Grok bots.

The native install, as of November 2026

Many Windows guides for Hermes still start with WSL2 and pin Python 3.13. Both are out of date. The platform support table now lists Windows 10 and 11, on x86_64 and aarch64, as Tier 1, and the Windows (Native) guide says it plainly: no WSL, no Cygwin, no Docker. The current release is v0.23.1, published November 10, 2026.

Open PowerShell and run:

iex (irm https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.ps1)

What that line does, from the guide:

  • No admin rights. It installs to %LOCALAPPDATA%\hermes\ and adds its bin folder to your User PATH, not the system one.
  • The installer sets up Python 3.14 for you; the package itself accepts >=3.11,<3.15. Any guide that insists on 3.13 is out of date.
  • Shell commands the agent runs go through Git Bash. The installer provisions Git for Windows if you do not have it.
  • Flags: -NonInteractive for scripted installs, -SkipBrowser and -SkipComputerUse to skip those tool sets, -IncludeDesktop to pull in the desktop app, and -Channel stable or main to pick a release channel.
  • Your state lives in %LOCALAPPDATA%\hermes\: user configuration, credentials, sessions, plugins, skills, and logs. A WSL install keeps its own in ~/.hermes.

Hermes Desktop, released as a public preview in June 2026, is a separate download for Windows, from the Microsoft Store or as an .exe, or pulled in by -IncludeDesktop. Hermes's platform table says the MSIX package needs Windows 11 22H2 or later; the desktop page itself lists Windows 10 and 11. Without the desktop app, the script install is still a full install; you just drive it from a terminal or a chat gateway.

What still breaks on Windows

Tier 1 means the project tests it, not that it never fails. These are the failures on the Hermes issue tracker and in community threads as of November 15, 2026.

  • No Python installed. #24424: the native install failed when Python was not installed. Closed in June 2026, and the installer now sets up Python 3.14 itself.
  • Dependency install failure on first run. #131199, opened October 2, 2026: a fresh native install fails at the Python-dependencies stage with "dependency install failed". Still open on November 15.
  • An update that deleted the gateway. #41255: hermes update removed the gateway-service/ folder and killed the Telegram gateway. Closed July 14, 2026. Worth knowing if your Telegram bot goes quiet after an update.
  • Running processes during an update. Hermes's updating docs say to quit Hermes Desktop first, and hermes update pauses a gateway started by the Scheduled Task on its own. If an update still fails on a locked file, quit every Hermes process and run it again.
  • PATH. The installer adds the folder to your User PATH, but the terminal you ran it in does not see the change. Close it and open a new one before hermes resolves.
  • Execution policy. If PowerShell refuses to run the script, the fix in community guides is to relax the execution policy for the current user. It is a community tip, not a step in the Hermes docs, so treat it as your call.
  • ARM64. Windows on ARM is Tier 1 for the Hermes CLI. The MausBot path below is x64 only, so on an ARM64 laptop the terminal route is the one that applies.

WSL2 or native?

Native. The official stance is not "use WSL2"; it is that both coexist, and you use WSL2 if you want POSIX fork or Linux file watchers. For a normal install where Hermes reads your files, runs commands, and talks to a model, native is the supported path and the one the installer is built for. The WSL2-first guides are out of date.

Running it as a service

Hermes's always-on mode on Windows is hermes gateway install. On Windows it registers a Scheduled Task named Hermes_Gateway that starts at your logon, with no admin rights; if group policy blocks scheduled tasks, it falls back to a hidden .vbs launcher in your Startup folder. It is not a Windows Service: it does not run before you sign in, and it shows up in Task Scheduler, not in services.msc. That is fine for a laptop you sign into every morning and the wrong tool for a headless box. For a Hermes that never sleeps, the hosting options are a separate post.

OpenClaw on Windows, briefly

OpenClaw is also officially native on Windows now, with more caveats. The Windows platform page lists four paths: Windows Hub, the recommended native app from the openclaw-windows-node repo (launched as OpenClaw Companion, with signed x64 and ARM64 installers and no admin rights needed), a Tauri backup app, the native CLI and Gateway through iwr -useb https://openclaw.ai/install.ps1 | iex, and a WSL2 install. The docs say "WSL2 remains the most Linux-compatible Gateway runtime on Windows," which is a weaker endorsement of native than Hermes gives its own Windows build.

Windows bugs on the tracker: a PATH mismatch between installer and shell (#19921, closed in March), a non-ASCII user profile path on GBK consoles (#150974, still open), and a Gateway console window that stayed visible (#138706, closed in September). Computer use on a paired Windows machine goes through the experimental cua-computer plugin: primary display only, no hold-key or separate mouse-down and mouse-up, no modifier arguments. And the exec approval default on gateway hosts is still full, meaning no prompt before a command runs. If you are choosing between the two, read our OpenClaw comparison and, if the machine will be a server, VPS vs Mac mini.

Hermes inside MausBot on Windows

MausBot, published on GitHub as OpenMausBot, is a native Windows x64 app: a chat app where every contact is an AI bot with its own model, its own computer, and its own connected apps. Hermes is one of its 16 agent engines, alongside Claude Code, Codex, Grok, Cursor, GitHub Copilot, Kiro, Kimi, Droid, Antigravity, OpenCode, Qwen, and Pi.

Setup on Windows is the install you already did: install Hermes with the line at the top of this post, run hermes setup to pick a provider, then create a bot in MausBot and choose Hermes as its engine. You bring your own provider, the way Hermes always has; no MausBot plan includes AI usage.

The MausBot model picker, with engines listed in a provider rail and Hermes selectable for a bot
Every bot picks an engine. Hermes sits in the same rail as Claude, Codex, and Grok, and you can switch mid-conversation.

What you get for it: a Windows desktop app with Hermes as one chat in the sidebar and Claude Code, Codex, or Grok bots in the others; group chats where a Chief of Staff bot hands work to the others; automations on a schedule, from a webhook, or on app events; Gmail, Slack, Notion, and hundreds more apps through a managed Composio service, plus any MCP server; and iPhone and Android apps for your bots. None of that needs a Telegram gateway.

Approvals follow MausBot's levels. Every new bot starts at Full access, where the engine runs in its most permissive mode, so a Hermes bot does not use Hermes's smart check unless you change the level; real questions and missing sign-ins still reach you. That is looser than Hermes's own default. Switch the bot or a single thread to Ask for approval, Auto-accept edits, or Approve for me, and set its sends on your behalf to Ask every time.

An Allow / Deny approval card in a MausBot chat, raised before a bot runs a shell command
With Ask for approval on, the request lands in the chat as a card.

Two more honest notes. A Hermes bot runs Hermes itself, so the bugs in the section above can still apply; if the native install fails, a Hermes bot will not work either. And the desktop app stops when your PC sleeps or is off, unless you turn on its Keep this computer awake setting.

Side by side

Four ways to get Hermes, or OpenClaw, onto a Windows machine. Each cell comes from the project's own docs or issue tracker.

Hermes native CLIHermes DesktopOpenClaw Windows HubHermes inside MausBot
InstallOne PowerShell line (install.ps1), no adminMicrosoft Store, an .exe download, or install.ps1 -IncludeDesktopSigned x64 and ARM64 installers, no admin; a Tauri backup app; or install.ps1 for the CLIMausBot's Windows x64 installer, plus Hermes from its own installer
Windows versionsWindows 10 and 11, x64 and ARM64Windows 10 and 11; the MSIX package needs Windows 11 22H2 or laterWindows 10 or 11, x64 or ARM64Windows x64
GUITerminal, or a chat gateway such as TelegramYesYes, Windows HubYes, a chat app with Hermes as one of the bots
Needs WSLNoNoNo; the docs call WSL2 the most Linux-compatible gateway runtimeNo
Always-onhermes gateway install, a Scheduled Task that starts at logonNot covered in this reviewGateway on port 18789While your PC is on and awake
Approval gateHermes's own modes: smart by default, manual, or offHermes's own modesExec approvals exist; the default on gateway hosts is full, no promptFull access by default, so Hermes runs in its most permissive mode; switch the bot to Ask for approval

Frequently asked questions

Does Hermes Agent run on Windows 11 natively?
Yes. Windows 10 and 11, on both x64 and ARM64, are listed as Tier 1 in the Hermes platform support table, the README calls native Windows fully supported, and the Windows (Native) guide says no WSL, no Cygwin, no Docker. The installer is one PowerShell line, needs no admin rights, and installs to %LOCALAPPDATA%\hermes.
Do I need WSL2 for Hermes Agent?
No. The official position is that native and WSL2 installs coexist, and that you pick WSL2 only if you want POSIX fork or Linux file watchers. Guides that say WSL2 first are out of date.
Is there a Hermes desktop app for Windows?
Yes. Nous released Hermes Desktop as a public preview in June 2026. On Windows it comes from the Microsoft Store, as an .exe download, or through the installer's -IncludeDesktop flag. Hermes's platform table says the MSIX package needs Windows 11 22H2 or later, while the desktop page lists Windows 10 and 11. A GitHub project called fathah/hermes-desktop is a separate third-party app.
Can I run Hermes inside MausBot?
Yes. Hermes is one of MausBot's 16 agent engines, next to Claude Code, Codex, Grok, and others, chosen per bot, and a Hermes bot can share group chats with the rest of your team. You install Hermes with its own installer and bring your own provider, the way Hermes always has.
Does OpenClaw run on Windows?
Yes, four ways: Windows Hub, the recommended native app with signed x64 and ARM64 installers; a Tauri backup app; the native CLI and gateway through a PowerShell one-liner; and a WSL2 install. The docs say WSL2 remains the most Linux-compatible gateway runtime on Windows.

Get started

Run the install.ps1 line above, open a new terminal, and run hermes setup to pick a provider. If you want the chat app around it, download MausBot for Windows, create a bot, and choose Hermes as its engine. The app is free and Apache 2.0 licensed; the source is on GitHub, and the iPhone and Android apps are shared on Discord. You pay only the provider you point Hermes at.

This post is based on the products as they were on . Products change. If something here is out of date, tell us and we will correct it.