Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Hermes Desktop creates separate HERMES_HOME instead of connecting to existing WSL installation

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The native Windows Hermes Desktop app does not detect or integrate with an existing WSL Hermes installation. Instead, it creates its own isolated environment under AppData\Local\hermes with a separate HERMES_HOME, config, sessions, and state.

Root Cause

The native Windows Hermes Desktop app does not detect or integrate with an existing WSL Hermes installation. Instead, it creates its own isolated environment under AppData\Local\hermes with a separate HERMES_HOME, config, sessions, and state.

RAW_BUFFERClick to expand / collapse

Description

The native Windows Hermes Desktop app does not detect or integrate with an existing WSL Hermes installation. Instead, it creates its own isolated environment under AppData\Local\hermes with a separate HERMES_HOME, config, sessions, and state.

Steps to Reproduce

  1. Have a working WSL Hermes setup (~/.hermes)
  2. Install and run the new Windows Hermes Desktop
  3. Observe that Desktop uses C:\Users\Don\AppData\Local\hermes and does not share config, MCP servers, or memory with the WSL instance

Connection Attempt

The Windows Desktop was pointed at the WSL backend IP using the remote gateway / remote backend option. Despite this, it still created and used its own isolated AppData\Local\hermes environment instead of delegating to the WSL instance.

Expected Behavior

Desktop should offer an option to connect to an existing remote WSL gateway/instance rather than forcing a parallel Windows installation.

Actual Behavior

Two completely separate Hermes environments run side-by-side with no easy way to bridge them.

Environment

  • Windows 10/11 + WSL2 (Ubuntu)
  • Hermes Desktop (native Windows version)
  • Existing mature WSL Hermes installation (6+ months, systemd services, 7 MCP servers)

Impact: Breaks the expected workflow for users who run Hermes primarily in WSL but want to use the Desktop UI.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING