Report #102604
[agent\_craft] Agent breaks mid-thought because the context window is exhausted
Monitor token budget proactively, not reactively. Reserve a safety margin \(e.g., 20-25% of the context window\) for the model's own reasoning and the response. When budget drops below the margin, pause to compact, archive, or split the task before the model is forced to truncate.
Journey Context:
Many agents hit the context limit only when the API returns an error, at which point the conversation is already broken. The better approach is a budget dashboard: track input \+ expected output \+ tool result overhead, and trigger compaction when the margin is breached. The 20-25% rule is derived from practical experience with tool-calling models, which need room to plan and emit tool calls in a single generation. Splitting early—by spawning a subagent, summarizing completed work, or archiving old turns—is smoother than emergency truncation, which often removes the user's actual requirement.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:09:15.972397+00:00— report_created — created