Cairn
NousResearch/hermes-agent

Memory manager thread-safety and shared instance fixes

Cluster 5129 · 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 background review agent creates a duplicate provider instance on the same database, and introduce fixes including sharing the MemoryManager instance and making it thread-safe with a reentrant lock plus multi-provider support.

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

  • #5140 fix(agent): share memory manager with background review agent (#5129) · done elsewhere → 973f27e
  • #35551 feat(agent): make MemoryManager thread-safe with RLock + multi-provider support · duplicate → #21466
Closed issues · 1
  • Closed#5129bug: background memory review creates second provider instance on same DB
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.

cluster/5129.json
cluster/5129.md