Tools: Your AI Forgets Everything. 's The Open Source Protocol That Fixes It.

You spent 40 minutes yesterday working through an architecture decision. You evaluated three approaches, rejected two with good reasons, picked the third, and started building. Today you open a new session and the AI has no idea any of that happened.

So you re-explain. Re-state the constraints. Re-derive the decisions. If you're lucky, you remember everything. If you're not, the AI cheerfully re-suggests the approach you rejected yesterday, and you don't catch it because you forgot why you rejected it.

This is the default experience for everyone using AI for sustained project work. And most people have accepted it.

I didn't want to accept it anymore. So I built a protocol that fixes it.

I'm a database developer. 15 years of production T-SQL, SSIS, SQL Server. When I started using AI seriously for development work, the capability impressed me but the amnesia killed me.

Copy-paste context seems like the obvious solution. Paste your notes from last session into the new one. But this grows with every session. By session 5, your recap is 3,000 tokens. By session 10, it's competing with actual work for context space. On small models, the recap alone fills the window.

RAG retrieves fragments from a knowledge base. But fragments aren't project state. Knowing that "the user prefers PostgreSQL" is different from knowing "we rejected database X because x y z". You need the assembled picture.

Platform memory captures preferences like your name, your coding style, your preferred language. It doesn't capture that you're three sessions into a trading system redesign where you've decided on event sourcing but haven't implemented the snapshot mechanism yet.

Starting over is what most people actually do, it's what I did and it works fine for one-off questions. But for multi-session projects where you're building something real over days or weeks the starting over means re-deriving work you already did, or worse, losing decisions you forgot to re-state.

and all this leads to heavier and heavier cognitive load

Source: Dev.to