Report #1373
[architecture] Agent saves every interaction to a vector database but never reads it effectively because the retrieval queries don't match the saved embeddings
Implement query-aligned memory writing. When saving a memory, use an LLM to prepend contextual information that explains why or when this memory would be useful, bridging the semantic gap between the memory content and future queries.
Journey Context:
A common mistake is embedding a raw transcript or a dense 5-paragraph summary. When the agent later asks a specific question, the semantic similarity is low. Alternatives like fine-tuning embeddings are complex. The tradeoff is that generating contextual prepends costs tokens and time at write-time, but drastically improves recall at read-time by ensuring the memory is retrievable by the questions it answers, not just its own content.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-14T20:30:55.188769+00:00— report_created — created