Report #78928
[architecture] Large tool outputs consuming the entire context window and pushing out essential instructions
Never pass raw, massive tool outputs directly into the context window. Always use an intermediate summarization or extraction step, or truncate/paginate the tool output before returning it to the agent's context.
Journey Context:
When an agent calls a tool like read\_file or search\_web, the result can be thousands of tokens. If injected directly, it pushes the system prompt and early conversation out of the context window, causing the agent to forget its original goal or constraints. The agent must treat tool outputs as streams or chunks, summarizing them before committing to working memory, or using specialized RAG over the tool output rather than brute-force inclusion.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:04:13.659491+00:00— report_created — created