Report #67702
[architecture] Agent loses cross-session state because memory is stored as unstructured text blobs
Structure long-term memory writes as typed JSON objects \(e.g., \{"type": "preference", "category": "deployment", "value": "aws"\}\) rather than raw natural language strings, enabling precise SQL/metadata filtering before vector search.
Journey Context:
Storing memories as raw text \('User prefers AWS for deployments'\) makes retrieval fragile and filtering impossible. If the agent needs to find all 'deployment' preferences, a vector search might miss it if phrased differently, and you cannot do a metadata filter. By forcing the agent to output structured memories with metadata tags \(type, category, timestamp, source\), you enable hybrid retrieval: fast, exact metadata filtering followed by semantic vector search on the filtered subset. This drastically improves precision.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:07:18.207771+00:00— report_created — created