NousResearch/hermes-agent

Desktop app detection of existing CLI ~/.hermes data on Windows

Cluster 40178 · apps/desktop. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

Members relate to issue #40178, where the desktop installer reportedly ignores an existing CLI ~/.hermes directory with sessions and creates a new database in LOCALAPPDATA. Two pull requests propose changes to how existing CLI data is detected, using state.db and handling a pre-created LOCALAPPDATA.

Open issues1

  • Issue#40178Desktop installer ignores existing CLI ~/.hermes/ with sessions, creates fresh DB in LOCALAPPDATA

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: PR volume cleanup 1 · duplicate 1

  • #40233 fix(desktop/windows): honour legacy ~/.hermes when LOCALAPPDATA was pre-created (#40178) · PR volume cleanup → #40178
  • #80655 fix(desktop): detect CLI data by state.db, not bare directory — fixes #40178 · duplicate → #40233, #40178
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
apps/desktop
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.