Report #64376
[synthesis] Agent loses original task context because retry loops fill context window with identical error messages
Implement exponential backoff with context deduplication: if an error message is identical to the previous one, do not append it to the context; instead, increment a counter and summarize \(e.g., Error X occurred 5 times\).
Journey Context:
Standard software engineering uses retries with backoff. LLM agents need this too, but they also need context management. Naively logging every retry causes the context window to fill with repetitive stack traces. Once the original prompt is evicted from the context, the agent forgets what it was doing and starts hallucinating new tasks. Deduplicating errors preserves the context budget for the actual task, treating the context window as the scarce resource it is.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:32:40.571316+00:00— report_created — created