User-level memories should be turned off by default
Project memory isolation feels especially important for B2B use cases.
If I’m working across multiple clients/projects, I’d expect project memories to never bleed into global context by default. Even small leaks could become a trust or legal issue in consulting/enterprise environments.
I ended up turning off global memories entirely for now, which solves it for me. But product-wise, I’d probably make global memory opt-in rather than automatic — similar to how Claude handles it. Then let users explicitly promote certain memories to global if they want. Seems like the challenge is building robust enough filtering/evals so only truly general things get extracted.
Status: Rejected
Log in to comment and vote
No comments yet
Be the first to share your thoughts.