Pluggable memory provider interface and integrations
NousResearch/hermes-agent · cluster 3943 · agent
Data as of
2 open items. Fix attempted, not merged.
The short answer
2open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue 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
- 2 issues and 0 PRs. Broad area: open items may be separate problems.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items concern designing and implementing a MemoryProvider interface that allows multiple memory backends (such as agentmemory) to be used as pluggable, isolated providers. Work spans interface definition, multi-provider support, and specific integration efforts.
Open issues2
Open PRs0
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#17119 feat(agent): support multiple simultaneous memory providers · superseded by another PR →
#5688
Closed issues · 1
- Closed#3943[Feature] Introduce `MemoryProvider` interface for long-term memory integrations
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.29: 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
- Closed issues
- 1
- Attempts
- 1 PR closed without merging