Official issues about installing and running on Windows. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
On Windows, hermes desktop launches Electron as a child process inheriting the parent PowerShell console, so closing the parent shell kills the Desktop app, and child process logs (including garbled encoding errors) flood the user's terminal.
On Windows, a benign unknown provider config key triggers a warning on every load_picker_context() call, and the resulting log volume deadlocks concurrent-log-handler's cross-process lock, stalling the asyncio event loop for ~14s at a time and dropping desktop/TUI WebSockets while /health stays green.
Operating a desktop app currently requires describing the window and controls in text; the proposal adds a way to attach a live window so the agent can see and control it via a UI-automation sidecar, already implemented per PR #53852.
Hermes on Windows uses the system's installed Node.js instead of its bundled version when the system Node.js is updated, causing version mismatches and terminal window flashing.
Switching models via the desktop chat model picker on Windows persists the change to the global config.yaml instead of scoping it to the current session, contrary to documented behavior.
This tracking issue consolidates roughly 25 reports of console windows (cmd, conhost, git, gh, powershell) flashing on the Windows desktop GUI when its windowless pythonw.exe backend spawns console-subsystem child processes without the no-window flag, and documents which spawn sites are still leaking based on source and git-history verification.
User requests native Windows support for Hermes Agent instead of running via WSL2. This issue is labeled as a duplicate.
Back to curated issues . School solution cards . Troubleshooting