Report #67950
[architecture] Agent loses its train of thought or forgets the instruction after a long-running tool execution returns
Inject a scratchpad or intent statement into the context immediately before the tool call, explicitly stating what the tool output should be used for.
Journey Context:
When an agent calls a tool, there is often a latency gap, and the tool returns a large payload. When the LLM resumes, it sees its own past reasoning, then a giant block of new text. It often loses the context of why it called the tool. By forcing the agent to write 'I am calling this tool to get X, which I will then use to do Y' before the call, you anchor the LLM's attention to its original intent when it resumes, preventing it from getting distracted by the tool's raw output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:32:01.910504+00:00— report_created — created