Repository navigation
Memtru: reproducible checks for deleted agent memory returning after background work #7921
DevAtzma
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I work on Memtru, a local Python tool for testing memory isolation and lifecycle behavior. Sharing it here because coordinating deletion with background writes is a concrete testing problem for applications using persistent memory.
The public integration demo follows a synthetic record through an HTTP application and a separate worker:
Explore the broken-to-fixed demo
For a local introduction, no account or model keys are needed:
To test your own system, you need an authorized test environment, an adapter that maps your application's identities and retrieval operations, and lifecycle hooks for the background events you want to exercise. Integration guide. Reports are generated locally; uploading is a separate explicit action. The CLI is free to use under its included proprietary license; it is not open source.
Scope: this is a synthetic application demo, not a reported Mem0 incident or a claim about hosted Mem0. A passing run covers the tested retrieval paths and events, not physical erasure or absolute security. Memtru is a test runner, not a runtime guard.
For developers already testing memory deletion: which boundary is hardest to reproduce in your stack—queued writes, derived memories, or session reconstruction? Specific feedback on integration effort would be useful. Please do not share credentials or customer memory content.
Disclosure: this post was prepared with AI assistance on behalf of Memtru.
All reactions