Design question I'd like blunt answers on. Picture memory that sits in the cloud, and every AI tool you use connects to it over MCP. At the start of a session the tool checks memory, at the end it saves what was decided. Each connected AI gets its own permissions, so a phone assistant might only read while the coding agent can read and write project decisions. Files stay where they are and get saved as links with a short description, so they show up in search. The part I keep going back and forth on is the write side: Auto-save at the end of every session. Nothing to maintain, but the model decides what's worth keeping, and a wrong conclusion sticks. Review queue. The AI proposes, you approve. Safer, but it's the same chore as keeping a DECISIONS.md current, which is the thing nobody does. Something in between, like auto-save for some tools and review for others. Which would you actually trust? And where does this design break for how you work? Background: I used to burn hours re-briefing AI tools on the same project, so I'm building this. No link, no name, I want the holes before I go further. If it worked the way you'd want, would you pay for it, or would you rather keep a markdown file and live with it?   submitted by   /u/Asly97 [link]   [comments]