Memory backend design and retrieval improvements
NousResearch/hermes-agent · cluster 2184 · agent
Data as of
Nothing open on GitHub. Fix merged in #22781. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #22781. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items explore different approaches to memory storage and retrieval for Hermes, including a holographic store, a video-based single-file backend (Memvid), structured fact extraction, and guidance constraints on what gets persisted.
Open issues0
Open PRs0
Fixes on record
-
#22781 fix(memory): tighten MEMORY_GUIDANCE against ephemeral PR/issue/SHA notes
files:
agent/prompt_builder.pyShow the diff
-
agent/prompt_builder.py@@ -157,6 +157,9 @@ def _strip_yaml_frontmatter(content: str) -> str: "User preferences and recurring corrections matter more than procedural task details.\n" "Do NOT save task progress, session outcomes, completed-work logs, or temporary TODO " "state to memory; use session_search to recall those from past transcripts. " + "Specifically: do not record PR numbers, issue numbers, commit SHAs, 'fixed bug X', " + "'submitted PR Y', 'Phase N done', file counts, or any artifact that will be stale " + "in 7 days. If a fact will be stale in a week, it does not belong in memory. " "If you've discovered a new way to do something, solved a problem that could be " "necessary later, save it as a skill with the skill tool.\n" "Write memories as declarative facts, not instructions to yourself. "
-
1 PR closed without merging
From the close comments: closed without comment 1
- #2351 feat(plugin): hermes-memory-store with holographic retrieval · closed without comment
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.39: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #22781
- Closed issues
- 2
- Attempts
- 1 PR closed without merging
- Fix link checked
- 9 May 2026