Hermes Agent adds native Windows support with PowerShell install

• Nous Research moved Hermes Agent's native Windows path out of beta, with NousResearch's announcement and Teknium's follow-up both pointing Windows users to a first-party PowerShell install instead of WSL-only workarounds.
• According to Teknium's docs link and the official Windows guide, the installer drops Hermes under %LOCALAPPDATA%\hermes, needs no admin rights, and wires hermes into the user PATH.
• The official repository install docs say the native path now covers the CLI, TUI, gateway, tools, and a bundled Git Bash, while the docs keep one notable exception: the dashboard's embedded terminal still needs WSL2.
• NousResearch's "big week" post and the v0.15.1 patch release place the Windows ship inside a broader Hermes push that also included the v0.15 Velocity release and follow-up hotfixes.

You can jump straight to the Windows guide, copy the one-line PowerShell installer from the repo, and cross-check the broader rollout in the v0.15.1 release notes. The docs also spell out a few unusually practical details: Hermes bundles PortableGit, falls back around flaky dependency installs, and keeps native Windows data separate from WSL data.

The native Windows command is a single PowerShell line:

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

The official Windows guide says that path installs into %LOCALAPPDATA%\hermes\, adds hermes to the user PATH, and does not require admin rights. The same page documents script parameters for pinning a branch, commit, or tag, skipping the virtualenv, or skipping the setup wizard.

The install flow is heavier than a thin wrapper script. According to the guide, it bootstraps uv, installs Python 3.11, installs Node.js 22, provisions portable Git if needed, clones the repo locally, creates a virtualenv, and runs a tiered uv pip install sequence so one flaky dependency does not collapse the entire setup.

The official repository install section and Windows guide both frame this as real native support, not a WSL shim. Hermes uses a bundled Git Bash on Windows for shell commands, the same basic strategy the docs explicitly compare to Claude Code.

The Windows feature matrix in the docs says native support now covers:

• CLI commands like hermes chat, hermes setup, and hermes gateway
• The interactive TUI
• Messaging gateways, including Telegram, Discord, Slack, and WhatsApp
• The cron scheduler
• The Chromium-based browser tool
• MCP servers over stdio and HTTP
• Local model backends such as Ollama, LM Studio, and llama-server
• The web dashboard, except its embedded terminal pane

That last caveat is the main holdout. The docs say the /chat terminal inside the dashboard still needs a POSIX PTY, so native Windows shows a WSL2-only banner there while the rest of the dashboard works normally.

Windows support landed during a noisy Hermes week. The official v0.15.1 patch release describes itself as a same-day hotfix for v0.15.0 after a dashboard infinite-reload bug, while Teknium's repost highlighted the bigger v0.15 changes: faster startup, roughly 4,500x faster session search, Kanban Swarm, and coding improvements.

Teknium's aside adds one small but useful clarification: some of the attention around the Windows announcement was about first-party packaging and docs, not a suddenly invented capability. The release notes and docs make the actual change clearer, the native Windows path now has an official, documented install surface that Nous is willing to ship as out of beta.

The official Quickstart keeps the onboarding order strict: run hermes setup, verify a real chat works, then add gateways, routing, or always-on deployments later. The same guide says Hermes expects a model with at least 64,000 tokens of context for multi-step tool calls and memory, which is an easy detail to miss if you only saw the Windows install clip.

That makes the Windows move less about opening a shell on a different OS and more about giving Windows users the same documented path into the full Hermes stack, provider setup included.