Report #45670
[architecture] Storing raw, unprocessed tool outputs in long-term memory
Summarize or extract structured entities from tool outputs before embedding them into the memory store; never embed raw JSON/HTML.
Journey Context:
When an agent fetches a large file or an API response, developers often embed the entire output. This creates noise: the embedding captures the generic structure of the API/JSON rather than the semantic meaning of the data. It also wastes vector DB space. The agent must process the output first—extracting the specific fact needed or summarizing it—before committing it to long-term memory.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:07:45.852595+00:00— report_created — created