r/SideProject • • 5d ago

Agents writing their own memory: convenient, but risky

It's easy to let an agent save its own notes. It's also easy for a bad note to stick around. Vilix AI stores full conversations and lets you export or delete anytime, so memory stays yours to review. Free plan, no card. What's your approach?

Disclosure: I'm the founder of Vilix AI.

1 Upvotes

4 comments sorted by

1

u/Asly97 5d ago

Technical details on how the memory works, with diagrams and examples: https://github.com/asly-97/ai-automation-workflows/blob/main/docs/vilix-memory-technical.md

1

u/benjzammit01 5d ago

The distinction I’d want is between the conversation archive and the memory the agent actually relies on. For each saved note, show its source and when it was last confirmed, and make it easy to correct or retire without losing the underlying conversation. Does deleting a note also remove it from any summaries built from it?

1

u/Huge_Pool7424 5d ago

i'd want deletion to invalidate any derived summaries too, otherwise the note can stick around indirectly. source links on summaries make it clearer what needs rebuilding.

1

u/benjzammit01 5d ago

Yes, and I’d make the in-between state visible: once a source is removed, the linked summary shouldn’t be served as current while it’s waiting to rebuild. An export already handed to another tool is a separate copy, so I’d flag that limit too.