Launch native Windows support in early beta
TL;DR
Hermes now runs natively on Windows via cmd.exe and PowerShell without requiring WSL. Includes a dedicated PowerShell installer and fixes for path normalization and process management.
What changed
Hermes Agent added native Windows support in an early beta release. The agent now runs directly through cmd.exe and PowerShell without WSL. A dedicated PowerShell installer handles setup, and updates fix path normalization plus process management.
The change removes the previous Linux-only requirement for self-hosted installs. Users on standard Windows machines can now run the same autonomous agent features.
Why it matters
Windows users gain direct access to persistent memory, auto-generated skills, and 16 messaging platform connections. This reduces setup friction for Vibe Builders who prefer native tools over virtual environments.
The move pressures competitors that still tie agents to Linux containers or WSL layers. It bets on wider adoption among solo operators who run mixed OS setups and want one agent across Telegram, Discord, and local scripts.
How to use it
Download the PowerShell installer from the Nous Research GitHub repository. Run it in an elevated PowerShell session on Windows 10 or 11.
After install, edit the YAML config to add bot tokens and start the agent with the standard CLI commands. Beta access is open now with no extra plan required beyond a free self-hosted VPS or local machine.
Watch for
Stable multi-day runs without path errors will confirm the beta holds up. Crashes during background process monitoring would break the current promise. Expect a follow-up release that adds equivalent native macOS support next.
Who this matters for
- Vibe Builders: Run autonomous agents on Windows via PowerShell to manage Discord and Telegram communities.
- Developers: Deploy Hermes natively on Windows without WSL to simplify local agent testing and path management.
Harsh’s take
Native Windows support for Hermes Agent is a smart distribution play. Most autonomous agent frameworks still force users into WSL or Docker, creating a high barrier for non-technical operators. By supporting cmd.exe and PowerShell directly, Nous Research is targeting the massive segment of solo operators who want to run bots locally without managing a Linux subsystem.
The technical challenge here is path normalization and process management, which often break when porting Linux-first tools to Windows. If Hermes maintains stability during multi-day runs, it becomes a top-tier choice for persistent local agents. This move signals a shift toward making high-capability agents accessible to the standard desktop user, moving beyond the developer-only sandbox.
by Harsh Desai
About Hermes Agent
View the full Hermes Agent page →All Hermes Agent updatesGo deeper
More AI news
- Daily RoundupGLM 5.3 and Vercel agent tools land, Gemini SAT practice, plus fresh models on Hugging Face
Google and Vercel released new agent and model features while Hugging Face and Replicate added trending models; OpenAI tightened safety after agent issues.
- Daily RoundupVercel-Origin beta and GPT-5.6 Sol discount, plus agent tools for builders
Vercel rolled out Origin repository deployments and a month-long GPT-5.6 Sol discount on AI Gateway while Product Hunt featured new agent layers and Hugging Face highlighted an uncensored Qwen model, with industry moves around data use and automation exits.
- Weekly DigestHermes Agent v0.20 voice and A2A protocol, OpenClaw mobile updates, and multi-agent tools to test now
Hermes Agent rolled out v0.20 releases with voice streaming, A2A interoperability, desktop artifacts, and self-recovery tools while OpenClaw added Android switching, iOS caching, and plugin provenance checks across the week.