[Feature] Bound repeated tool-validation failures while allowing corrected calls
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading #7388 and #7387 for the existing repeated-call notices, then review the runner and tool-validation paths that classify failures before execution. The issue calls for agreement on the threshold, opt-in mechanism, and error classification before a general implementation; verify that corrected calls and successful repeated calls remain available, while unchanged validation failures are bounded within one run.
Written by the indexing model from the issue text.
Description
Feature Description
Provide a bounded recovery policy for repeated, deterministic tool-validation failures while allowing corrected requests to proceed.
In a scheduling incident, the agent made 16 invalid future_task(action="create") calls: 12 omitted the one-time switch and four later omitted reminder content. All failed before persistence. Repeated-call notices were logged, but the run continued making invalid calls.
#7388 already supplies escalating notices after repeated calls. This discussion concerns what should happen when the model continues submitting the same arguments and receives the same deterministic validation error despite those notices.
Proposed Behavior for Discussion
- Identify pre-execution validation failures reliably, preferably through explicit error classification rather than matching arbitrary error text.
- Track the same tool, equivalent arguments, and validation failure within one run. Reset the streak when arguments are corrected or execution succeeds.
- After a small bounded number of unchanged failures, stop executing that offending tool for the current run and have the agent report that the requested operation was not completed. Keep unrelated tools available and restore normal availability on the next run.
- Preserve successful repeated calls and legitimate polling; a repeated tool name alone is insufficient evidence of failure.
- Treat uncertain outcomes such as network timeouts separately. A create request may already have succeeded, so state verification and request idempotency need separate design rather than blind retry.
The threshold, tool opt-in mechanism, and error classification should be agreed before implementing a general runner change. A local future_task-specific mitigation has been isolated and tested, but this issue does not propose importing the broader #6259 patch or claim a generic solution is already implemented.
Use Case
Natural-language reminders and other state-changing tools whose missing arguments can otherwise consume the entire agent step budget without making progress. The focused companion fix for one-time reminder inference is #11085, addressing #11084.
Related Work
- #6259: closed, unmerged proposal containing error-loop protection and other mechanisms.
- #7388 and #7387: repeated-call notices and the original looping report.
- #8163: configurable notice thresholds; related, but does not itself specify a bounded response to deterministic validation failures.
Checklist
- Searched existing issues and PRs; related and historical proposals are linked above.
- This concerns AstrBot core rather than a plugin.
- Read and will follow the project Code of Conduct.
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 3.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 136
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AstrBotDevs/AstrBot
-
[Bug] Sending a Telegram message chain twice duplicates mentionsPossibly taken @123XieC claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AstrBotDevs/AstrBot#11125 ·
Maintainers usually reply within 1 day
-
[Bug] Telegram album debounce exceeds the maximum waitPossibly taken @123XieC claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AstrBotDevs/AstrBot#11123 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AstrBotDevs/AstrBot#11034 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug] OpenAI-compatible Gemini 工具 schema const 导致 400Possibly taken @arccat-114 claimed this 26 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
AstrBotDevs/AstrBot#10720 · 1 comment ·
Maintainers usually reply within 1 day
-
[Bug] Discord slash command sync aborts with KeyError when a plugin handler is defined in a submodulePossibly taken @yuexia5 claimed this 31 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
AstrBotDevs/AstrBot#10626 · 1 comment ·
Maintainers usually reply within 1 day
All issues in AstrBotDevs/AstrBot
Similar issues
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 79/100
gregwebs/agent-vm-images#216 ·
Maintainers usually reply within 1 day
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gcivil-nyu-org/team5-mon-fall26#145 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gcivil-nyu-org/team3-mon-fall26#156 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
antlr/grammars-v4#5220 ·
Maintainers usually reply within 1 day