Gating legacy memory tool visibility and configuration

NousResearch/hermes-agent · cluster 57793 · agent

Data as of

2 open items. Fix merged in #90559. Check it covers your case.

The short answer

2open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #90559. 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
2 issues and 0 PRs.

These issues and PRs concern controlling when the legacy/built-in memory tool is shown or active, specifically hiding it when memory is disabled or an external memory provider is configured. Related work includes renaming a configuration flag to better reflect its scope.

Open issues2

  • Issue#57793Legacy memory tool should be gated when an external memory provider is configured
  • Issue#60805Legacy memory tool visible when memory_enabled: false (conflicts with Mnemosyne)

Open PRs0

No open pull requests.

Fixes on record

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

  • #90559 fix(memory): disabled built-in stores no longer leave a dead memory tool and guidance in every prompt (salvage #90413)

    merged to main

    files: agent/prompt_builder.py, agent/system_prompt.py, tests/agent/test_builtin_memory_disabled_surface.py, tests/run_agent/test_run_agent.py, tools/memory_tool.py, website/docs/user-guide/features/memory.md

3 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1 · other 1

  • #57798 fix(memory-tool): gate legacy memory tool when external memory provider is configured (Closes #57793) · other
  • #60817 fix(memory): hide legacy tool when memory_enabled: false · done elsewhere → #90559, #90413
  • #84787 fix(memory): rename memory_enabled to builtin_enabled, gate the built-in tool on the store predicate · superseded by another PR → 2cf7b36, d5cddae, a969c5a
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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
Merged PRs
#90559
Closed issues
0
Attempts
3 PRs closed without merging
Fix link checked
20 Aug 2026

For your agent

The same facts, typed.