Repository navigation
[FEATURE]: Improve doom loop detection granularity #32187
Description
Activity
This issue might be a duplicate of existing issues. Please check:
- bug(processor): doom loop detection misses cross-message repetitions and has inverted filter order #25254: doom loop detection misses cross-message repetitions and has inverted filter order — directly overlaps with the concern about tool name-only matching
- [FEATURE]: Make doom_loop repeat threshold configurable #23531: Make doom_loop repeat threshold configurable — similar request to improve/tune detection granularity
- Agent loops 277 times on MCP resource_list without circuit breaker #31942: Agent loops 277 times on MCP resource_list without circuit breaker — referenced in your issue, also covers detection gaps
Metadata
Metadata
Assignees
Labels
No labels
Motivation
DOOM_LOOP_THRESHOLD = 3 (processor.ts) only triggers when both tool name AND input parameters match exactly (JSON-serialization comparison). Slight parameter variations (e.g., editing different lines) bypass the detection entirely.
Details
Related: #31942