Report #14658
[architecture] Storing memories globally across all users or sessions causes the agent to leak private context from one user to another
Namespace or partition vector stores and memory graphs by a strict user\_id or session\_id scope, and apply mandatory metadata filters on every retrieval query.
Journey Context:
It is easy to set up a single vector index and dump all embeddings into it. But without strict metadata filtering on retrieval, a query from User A might retrieve User B's API preferences or personal data. Metadata filtering is not an optional feature; it is a core architectural requirement for multi-tenant memory systems to prevent cross-contamination and security breaches.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:10:35.301890+00:00— report_created — created