Cairn
NousResearch/hermes-agent

Lazy qdrant path resolution for HERMES_HOME support

Cluster 85830 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These members address a bug where mem0's qdrant default path is evaluated at import time, preventing HERMES_HOME environment variable redirection from taking effect. The fixes defer path resolution to use time so the correct path is honored.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #85941 fix(mem0): resolve qdrant path lazily to honor HERMES_HOME · duplicate → #63961
  • #86167 fix(memory/mem0): resolve qdrant default path from HERMES_HOME at use time · superseded by another PR → #63961, #85830
Closed issues · 1
  • Closed#85830mem0 qdrant default path is frozen from HOME at import time, so HERMES_HOME redirection cannot reach it
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/85830.json
cluster/85830.md