NousResearch/hermes-agent

Memory tool false drift detection and refusal fixes

Cluster 107270. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #133038 on 5 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #133038. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #133038. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #133038, then check it covers your case.

Read #133038 Pick up a Lab task

These issues and fixes address the memory tool incorrectly refusing write operations by misidentifying file drift, including cases where MEMORY.md matches its backup exactly or differs only in formatting. The work involves bounding refusal behavior and reducing spurious backup file clutter.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#133038 Memory writes stop failing on hand-formatted files, and refused writes say exactly what to fix (#107270, #90468)

merged to main

files: tests/agent/test_learning_mutations.py, tests/tools/test_memory_tool.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 1 · superseded by another PR 1

#107278 fix(memory): ignore format-only MEMORY.md drift on replace · done elsewhere → b901358, #133038, #107270
#107280 fix(memory): bound the external-drift refusal and stop duplicate .bak clutter (#107270) · superseded by another PR → #107278, #107270

Closed issues · 1

Closed#107270memory tool falsely refuses writes: reports file drift when MEMORY.md matches its backup byte-for-byte

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.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

Merged PRs: #133038
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 5 Oct 2026

For your agent

The same facts, typed.

cluster/107270.json
cluster/107270.md