Memory provider system prompt block gating fix
NousResearch/hermes-agent · cluster 81014 · agent
Data as of
Nothing open on GitHub. Fix merged in #94446. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #94446. 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 the memory provider's system_prompt_block() was injected unconditionally while the associated tools were gated by platform toolset configuration, causing agents to receive instructions for tools not present in their tool surface. The fix gates the system prompt block on the same toolset check used for tool injection.
Open issues0
Open PRs0
Fixes on record
-
#94446 Memory provider prompt guidance no longer appears when its tools are gated off (#81014, salvage #81058)
files:
agent/memory_manager.py,agent/system_prompt.py,tests/agent/test_memory_provider.py,tests/agent/test_system_prompt.py
4 PRs closed without merging
From the close comments: superseded by another PR 3 · merged via another change 1
-
#81058 fix(agent): gate memory provider system_prompt_block on toolset config (#81014) · merged via another change →
8172be0,#94446 -
#81068 fix(memory): gate system_prompt_block() on the same toolset check as tool injection (#81014) · superseded by another PR →
#81058 -
#81078 fix(agent): gate memory provider system_prompt_block on tool availability (#81014) · superseded by another PR →
#81058 -
#81089 fix(memory): gate provider system-prompt block on the toolset gate · superseded by another PR →
#81058
Closed issues · 1
- Closed#81014Memory provider system_prompt_block() injected unconditionally while provider tools are gated by platform_toolsets — agent receives instructions for tools that don't exist in its tool surface
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.33: 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
- Subsystem
- agent
- Merged PRs
- #94446
- Closed issues
- 1
- Attempts
- 4 PRs closed without merging
- Fix link checked
- 25 Aug 2026