[Feature] Bound repeated tool-validation failures while allowing corrected calls
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Python
- Sterne
- 46.9k
- Forks
- 3.6k
- Ø Merge
- 1 T. 6 Std.
- Gemergte PRs (30 T.)
- 136
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus AstrBotDevs/AstrBot
-
[Bug] Sending a Telegram message chain twice duplicates mentionsEvtl. vergeben @123XieC hat das vor 5 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
AstrBotDevs/AstrBot#11125 ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug] Telegram album debounce exceeds the maximum waitEvtl. vergeben @123XieC hat das vor 5 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
AstrBotDevs/AstrBot#11123 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
AstrBotDevs/AstrBot#11034 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug] OpenAI-compatible Gemini 工具 schema const 导致 400Evtl. vergeben @arccat-114 hat das vor 26 Tagen übernommen. Offenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
AstrBotDevs/AstrBot#10720 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
[Bug] Discord slash command sync aborts with KeyError when a plugin handler is defined in a submoduleEvtl. vergeben @yuexia5 hat das vor 31 Tagen übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
AstrBotDevs/AstrBot#10626 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in AstrBotDevs/AstrBot
Ähnliche Issues
-
cognition
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
collabnix/awesome-mcp-lists#433 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
CrossEntropyFilter raises on zero probabilities and single-class resultsEvtl. vergeben @NopeCharon hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
datajoint/datajoint-python#1703 ·
Maintainer antworten meist innerhalb von 6 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Archmonger/ServeStatic#129 ·