Report #55949
[architecture] Storing tool execution results directly in long-term memory
Store only the summary or schema of tool outputs in agent memory, and persist the raw outputs in a separate document store \(e.g., S3, local disk\) referenced by URI.
Journey Context:
When an agent reads a 100-line file or gets a large JSON API response, storing that in the vector DB or context window destroys efficiency and dilutes retrieval quality. The agent should save the raw data to a file/DB, get a pointer \(URI/path\), and store the pointer \+ a brief summary in its memory. This keeps memory lightweight and retrieval high-signal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:24:19.048804+00:00— report_created — created