Cairn
NousResearch/hermes-agent

Hermes profile name resolution via symlink overlays

Cluster 93862 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 1 PR.

A bug report and two related fixes address incorrect active profile detection when HERMES_HOME points to a symlink-farm overlay directory rather than a standard profile path. The work focuses on resolving the correct profile identity in the agent under this directory layout.

Open issues1

  • Issue#93862[Bug]: "Active Hermes profile" resolves to "default" when HERMES_HOME is a custom overlay directory (symlink farm into <root>/profiles/<name>)

Open PRs1

  • PR#101855fix(agent): resolve profile name from symlink-farm overlay homes

1 PR closed without merging

From the close comments: other 1

  • #93921 fix(agent): resolve profile identity for symlink-overlay HERMES_HOME dirs · other → #97165, #93862, #84867
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/93862.json
cluster/93862.md