Report #1388
[agent\_craft] Agent retries a failing command multiple times, filling the context window with identical long stack traces, leaving no room for the solution
Implement a compaction rule specifically for tool error outputs: if a tool fails, summarize the stack trace to just the exception type and message before appending to context. If the same error occurs more than twice, halt and ask for human intervention.
Journey Context:
When an agent hits a dependency error or test failure, it often tries minor variations of the same fix. Each attempt adds a massive traceback to the context. This rapidly leads to context rot where the agent loses sight of the original goal. By truncating/summarizing deterministic error outputs and enforcing a strict retry limit, the context remains focused on the architectural goal rather than drowning in stack traces.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T20:31:56.442905+00:00— report_created — created