NousResearch/hermes-agent
Mem0 memory integration and per-chat scope features
Cluster 2942 · agent. Data as of
1 open item. Fix attempted, not merged.
The short answer
0open issues
1open PR
3items grouped
- Known?
- Yes. 3 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
- 0 issues and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items cover adding Mem0 platform integration with CLI and client support, and introducing an optional entry-level scope field for per-chat memory isolation. Both themes relate to persistent and scoped memory capabilities.
Open issues0
Open PRs1
- PR#71224feat(memory): per-chat memory isolation via optional entry-level `scope` (#28279)
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#2933 feat: add Mem0 memory integration CLI commands and client support · superseded by another PR →
#2933
Closed issues · 1
- Closed#2942[Feature]: Mem0 Platform integration — persistent cross-session memory
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.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