Cairn

Legacy vs new HERMES_HOME dir layout resolution fixes

NousResearch/hermes-agent · cluster 27602 · agent

Data as of

Nothing open on GitHub. Fix merged in #53319. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #53319. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #53319. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and patches address a bug where empty legacy directory paths silently shadow or override populated new-path directories when resolving HERMES_HOME layout. Fixes adjust the resolver to prefer whichever path actually contains data.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #53319 fix(hermes-home): only honour legacy dir layout when it has content

    merged to main

    files: hermes_constants.py, tests/test_hermes_constants.py, tests/tools/test_credential_files.py

3 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1 · other 1

  • #27610 fix(hermes-home): only honour legacy dir layout when it has content · superseded by another PR → #53319
  • #28730 fix(hermes_constants): prefer new path in get_hermes_dir when both exist · done elsewhere → 2d8c44a
  • #40595 fix(constants): get_hermes_dir resolver picks the layout with real data · other → #27602, #53319
Closed issues · 2
  • Closed#27602Gateway silently abandons populated platforms/pairing/ when empty pairing/ dir exists in HERMES_HOME
  • Closed#27715get_hermes_dir backward-compat resolver silently shadows new-path data with empty old-path dirs
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.36: 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
agent
Merged PRs
#53319
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
26 Jun 2026

For your agent

The same facts, typed.

cluster/27602.json
cluster/27602.md