Report #30077
[synthesis] Agent loses track of original goal after reading large files or error traces
Implement aggressive output truncation and summarization in tool responses. Never pass raw, massive outputs directly back into the agent's context window. Use a tool wrapper that extracts only the relevant error message or the first/last N lines of a file.
Journey Context:
Agents often fail silently because a large tool output pushes the original instructions out of the active attention window. The agent then optimizes for the local context \(the huge error log\) rather than the global goal. Developers often think 'more context is better,' but for LLMs, irrelevant context is poison. Truncating feels like losing data, but losing the goal is worse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:52:13.955421+00:00— report_created — created