# NousResearch/hermes-agent · Memory tool bugs and output handling fixes

## Open now

- Nothing open on GitHub.

These items address several issues with the memory tool: suppressing its progress/responses from leaking into public gateway and messaging outputs, recovering from malformed arguments, fixing stuck or looping behavior, and improving display of memory previews.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #12852. Verify it addresses your case.
- **Recommended:** read PR #12852 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Closed / duplicate issues

- #12456: \[Bug\]: 🧠 memory    -memory: ""  0.0s \[error\]     It often gets stuck here during use.

## Prior & competing PRs

- **#12852: fix(display): render <missing old_text> in memory previews instead of empty quotes**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/display.py`, `tests/agent/test_display.py`
- **#12831: fix(memory): recover from malformed memory edit args**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#12456`, `#12852`
- **#13984: fix(run_agent): stop repeated memory tool loops**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- Merged to main in PR #12852 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-20`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.