I built this because I kept using different AI tools for different things, and got pretty tired of re-explaining the same stuff over and over.
ChatGPT knew a few things about me, Claude knew some other things, Gemini had basically none of it, and switching between them always felt a bit dumb.
So this is my attempt at a portable memory layer.
Right now the idea is pretty simple:
YourAIScroll
Mailwarm
Hello @zhengyang_hou ! Congratulations...
how do you prevent the Memory.md file from degrading over time once users start accumulating conflicting instructions across different assistants? is there any conflict resolution layer when platforms disagree on what the user is or prefers?
YourAIScroll
@thamibenjelloun Great question. I’m treating that as a curation problem, not a blind merge problem. Memory Sync is intentionally human-in-the-loop right now because I don’t think long-term memory should auto-merge silently across assistants. Different platforms can infer different things, and some of that will be noisy or contradictory.
So the current model is: pull memory out, review it in one editable Memory.md, compress / clean it up, then push forward only what should persist. In other words, conflict resolution currently happens through user review, not hidden automation. Longer term, I do think there’s room for better structure, conflict flags, and suggested deduplication, but I wanted the first version to optimize for transparency and control.