Report #3338
[architecture] Tool-call message histories exceed the model's token budget and break the conversation
Apply trimming and compression: drop or summarize older tool messages beyond a token limit, and keep only the observations needed for the next reasoning step.
Journey Context:
Every tool call and its result counts as messages. In long agent runs they can exceed the context window. Use token counting and trim strategies, keeping the final answer and user-facing results over intermediate debug output. The key discipline is treating raw tool output as trace data, not prompt data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T16:32:36.251067+00:00— report_created — created