Skills read tools missing from idempotent guardrail list
NousResearch/hermes-agent · cluster 30408 · agent
Data as of
Nothing open on GitHub. Fix merged in #100967. Check it covers your case.
The short answer
- Known?
- Yes. 8 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #100967. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #100967. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where skills_list and skill_view are read-only tools but were absent from IDEMPOTENT_TOOL_NAMES, causing repeated identical calls to go undetected by the tool-loop guardrail. Multiple fixes and related agent guards address this gap.
Open issues0
Open PRs0
Fixes on record
-
#100967 fix(guardrails): tool-call loops hard-stop on unattended platforms, identical replays halt for any tool (#49075, #89069; salvage #49189, #47231)
files:
agent/agent_init.py,agent/tool_guardrails.py,cli-config.yaml.example,hermes_cli/config_defaults.py,run_agent.py,tests/agent/test_tool_guardrails.py,tests/run_agent/test_tool_call_guardrail_runtime.py,website/docs/user-guide/configuration.md,website/docs/user-guide/docker.md
5 PRs closed without merging
From the close comments: merged via another change 2 · superseded by another PR 2 · duplicate 1
-
#47231 fix(agent): guard repeated skill reads · merged via another change →
25d954c,#100967,#49075 - #49092 fix(guardrails): add skills_list/skill_view to IDEMPOTENT_TOOL_NAMES · superseded by another PR
-
#49101 fix(guardrail): add skills_list and skill_view to IDEMPOTENT_TOOL_NAMES · duplicate →
#47231,#49092,#49075 -
#49202 fix(agent): guard repeated skill read tool calls · merged via another change →
25d954c,#100967,#47231 - #54411 fix(guardrails): add skills_list/skill_view to IDEMPOTENT_TOOL_NAMES · superseded by another PR
Closed issues · 2
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.23: 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
- #100967
- Closed issues
- 2
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 2 Sep 2026