[Feature] Bound repeated tool-validation failures while allowing corrected calls

Offen
#11,086 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

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
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
python
Bereich
ai, backend

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

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AstrBotDevs/AstrBot

Alle Issues in AstrBotDevs/AstrBot

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.