NousResearch/hermes-agent

Holographic memory db_path portability fix

Cluster 119743. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #120062 on 23 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #120062, then check it covers your case.

Read #120062 Pick up a Lab task

A bug where holographic memory stores a concrete db_path causes cloned profiles to share a fact DB and renamed profiles to lose their facts. The fix stores the path using $HERMES_HOME so each profile maintains its own independent fact store.

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.

#120062 fix(memory/holographic): store the default fact DB path as $HERMES_HOME so clones and renames keep their own store

merged to main

files: plugins/memory/holographic/__init__.py, tests/plugins/memory/test_holographic_profile_db_path.py

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

#119744 fix(memory/holographic): store the default fact DB path as $HERMES_HOME, not the profile's concrete path · merged via another change → 646749d, #120062
#119788 fix(memory): store holographic db_path portable so clones and renames keep their own fact DB · duplicate → 9fe737a, 1c2734b, 5c6b56a, #119788, #119744, #120062

Closed issues · 1

Closed#119743[Bug]: Holographic memory setup writes the profile's concrete db_path, so a cloned profile shares the source's fact DB and a renamed profile loses its facts

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.50: 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

Merged PRs: #120062
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/119743.json
cluster/119743.md