Report #8652
[architecture] Saving large raw API responses as long-term memories
Never persist raw JSON or text payloads from tool outputs directly into the vector store. Always extract only the minimal state delta or the specific answer required for future steps, and discard the rest.
Journey Context:
When an agent calls an API \(e.g., fetching a list of files or a large JSON payload\), it often saves the entire output to remember it later. This bloats the vector store with highly volatile, unstructured, and redundant data that fragments context windows upon retrieval. The tradeoff is the need to re-fetch data if the exact details are lost vs. maintaining a lean, high-signal memory store that doesn't poison the context with outdated API dumps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:09:20.462343+00:00— report_created — created