Cairn
NousResearch/hermes-agent

Mem0 config secrets and memory read fixes

Cluster 25085 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
1 issue and 0 PRs.

These items address bugs in the Mem0 integration: preventing API keys from being written inline into mem0.json, and fixing how agent-attributed memories are read. The changes involve config serialization and memory retrieval behavior.

Open issues1

  • Issue#25085[Bug/Practice]: Mem0 setup writes API key inline in mem0.json on some install paths

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #25425 fix(mem0): exclude secret fields from mem0.json on save_config · other → 781334e, #133822
  • #38429 fix(mem0): read agent-attributed memories · done elsewhere
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
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/25085.json
cluster/25085.md