staged memory approval deletes wrong entry silently
Cluster 120841. Data as of
Nothing open on GitHub. Fix merged in #121275 on 24 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #121275. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where approving a staged memory removal or replacement could silently affect a different, newer entry than the one the approver actually reviewed. These items track the bug report and fixes to make staged destructive approvals target only the exact reviewed entry.
Open issues0
Open PRs0
Fixes on record
-
#121275 Approving a staged memory replace/remove changes only the reviewed entry (#120841, salvage #120842)
files:
hermes_cli/write_approval_commands.py,tests/tools/test_memory_tool.py,tests/tools/test_write_approval.py,tools/memory_tool.py,tools/memory_tool_store.py,website/docs/user-guide/features/memory.md
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#120841[Bug]: approving a staged memory remove deletes a newer entry the approver never saw, silently
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.50: 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
- Merged PRs
- #121275
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 24 Sep 2026