In the walrus implementation I notice there is no explicit programmable way to delete or forget memories.
Rather there is a manual workaround: https://docs.wal.app/walrus-memory/guides/delete-old-memories
My suggestion: Create a function to delete memories.
await memwal.forget(blobId)
// or
await memwal.forgetByQuery("peanut allergy", namespace)
Why?
In a system context, it gives developers the flexibility to build logic to prune memory periodically, like I would like the ability to be able to delete memories that conflict, over time.
Like let's say I saved to the memory that "I love python for machine learning" in January early in the year; by march if I save to the memory that "I now find, Go to be much faster and more exciting for machine learning, as it scales better than python, in a cloud infrastructure ".
This would let developers implement memory lifecycle policies directly in code.
Depending on the application, I may want to explicitly retire the older memory instead of keeping both indefinitely. Besides giving developers more control, it can reduce unnecessary storage, improve retrieval quality, and keep long-running agents' memory stores clean.
Just my honest feedback 💙
Love Walrus nice work guys
In the walrus implementation I notice there is no explicit programmable way to delete or forget memories.
Rather there is a manual workaround: https://docs.wal.app/walrus-memory/guides/delete-old-memories
My suggestion: Create a function to delete memories.
Why?
In a system context, it gives developers the flexibility to build logic to prune memory periodically, like I would like the ability to be able to delete memories that conflict, over time.
Like let's say I saved to the memory that "I love python for machine learning" in January early in the year; by march if I save to the memory that "I now find, Go to be much faster and more exciting for machine learning, as it scales better than python, in a cloud infrastructure ".
This would let developers implement memory lifecycle policies directly in code.
Depending on the application, I may want to explicitly retire the older memory instead of keeping both indefinitely. Besides giving developers more control, it can reduce unnecessary storage, improve retrieval quality, and keep long-running agents' memory stores clean.
Just my honest feedback 💙
Love Walrus nice work guys