I stopped storing chats and built a stateful study agent instead !!
My study assistant kept forgetting everything. Not after a day — after one message. That turned out to be a design problem, not a model problem. What this is My team and I built a single-page app t...

Source: DEV Community
My study assistant kept forgetting everything. Not after a day — after one message. That turned out to be a design problem, not a model problem. What this is My team and I built a single-page app that combines a few things students usually use separately: A Pomodoro timer with session tracking Flashcards with feedback loops A quiz system that logs mistakes A simple chatbot Progress tracking like XP, streaks, and subjects Everything runs in the browser. No backend. Data is stored locally. The interesting part isn’t the features — it’s how they all feed into a shared memory layer. The problem: fake memory The first version of the chatbot didn’t actually remember anything. You could tell it you’re weak at something, and in the very next message it would ignore that completely. It wasn’t because the model was bad. It was because every interaction was stateless. Each message was treated like a fresh start. What I tried first We started with the obvious approach: pass previous messages back