NousResearch/hermes-agent

Mem0 read filter missing agent-attributed memories

Cluster 38424 · 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 items address a bug where the Mem0 provider's read filter did not include memories attributed to agents. The fix updates the filter logic to correctly retrieve agent-attributed memories.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #38429 fix(mem0): read agent-attributed memories · done elsewhere
  • #38444 fix(mem0): include agent-attributed memories in read filter (closes #38424) · duplicate → #38429, #38424
Closed issues · 1
  • Closed#38424Mem0 provider read filter misses agent-attributed memories
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.