Operate Hermes Natively on Windows

Hermes can run directly on Windows 10 or 11 without WSL. Native mode fits workflows that must work naturally with Windows paths, applications, browsers, scheduled tasks, and local services.

Operating checklist

Run the official PowerShell installer as the normal user.
Open a fresh terminal after PATH changes.
Confirm the intended Windows HERMES_HOME.
Select only needed providers and tools.
Treat Git Bash as the terminal-tool shell.
Stop locking processes before updates.

How the workflow works

The CLI, TUI, gateway, cron scheduler, browser tool, MCP servers, local-model clients, and most dashboard features run natively. The dashboard embedded terminal pane needs a POSIX PTY and remains a WSL2-oriented surface. The terminal tool uses Git Bash, while the installer manages Python, Node, PortableGit, and optional dependencies under the user data directory. Hermes also configures UTF-8 early to avoid console encoding failures.

Common pitfalls

Typing PowerShell syntax into a Git Bash tool call.
Expecting the embedded dashboard terminal pane.
Updating while Desktop or the gateway locks the environment.
Maintaining native and WSL installs as if they share state.

Verification steps

Run hermes version in a fresh PowerShell.
Run hermes doctor.
Complete a harmless Git Bash command through Hermes.
Test required browser or MCP tools.
Start the gateway and verify hermes gateway status.

Use the official Hermes documentation for the current source of truth.