Transcript sanitiser loop detection and escalation
Cluster 96870 · agent. Data as of
2 open items. Fix merged in #99687 on 31 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #99687. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #99687. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
These items address a problem where the transcript sanitiser repeatedly triggers without surfacing meaningful feedback, adding counters, escalation policy, and a one-time user notice to make repeated healing loops visible rather than silent.
Open issues0
Open PRs2
Fixes on record
-
#99687 feat(agent): escalate repeated transcript-sanitiser heals — counters, one ERROR, one-time user notice (#96870)
files:
agent/agent_runtime_helpers.py,agent/conversation_loop.py,cli-config.yaml.example,hermes_cli/config_defaults.py,hermes_cli/debug.py,hermes_cli/dump.py,tests/run_agent/test_sanitiser_escalation.py
Closed issues · 1
- Closed#96870Silent recovery mode: sanitiser + Telegram adapter silently loop while user/agent sees nothing
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.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
- #99687
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 31 Aug 2026