When Claude starts to forget
You’re an hour into a big task. It’s going well. Then Claude asks about a file you already walked it through, or quietly drops a rule you set at the very start (“don’t touch anything outside src/auth/”). It feels like it suddenly got worse — like the further you go, the dumber it gets.
Claude didn’t get dumber. The space it can hold in mind filled up, and the oldest things slid off the edge first.
That’s a completely different problem from a conversation going off the rails — and it has a completely different fix. Last lesson the conversation went bad. This time it’s going fine; it’s just gotten long.
The desk that fills up
Everything in a conversation — your task, the files Claude’s looking at, every message so far — has to sit in one finite space called the context window.
The context window is the model’s desk. Your question, the open files, the whole back-and-forth — it all has to fit on the desk at once. The desk is big, but it isn’t infinite.
A short chat barely covers the desk. But a long, productive session — twenty files read, fifty messages, a plan, a pile of TODOs — eventually fills it. And when the desk is full, something has to give. What gives is the oldest stuff: the file you looked at first, the constraint you set in message one. It slides off the edge to make room for what’s happening now.
So the “forgetting” isn’t random and it isn’t a defect. It’s the predictable result of a full desk. Which means the fix isn’t to explain harder — it’s to clear some desk.
Two ways to clear the desk
You already know one of them. /clear, from the off-the-rails lesson, empties the desk completely — everything gone, blank slate. That’s exactly what you want when the conversation has turned to junk, or when you’re starting something unrelated. But in the middle of a long task that’s going well, emptying the desk throws out an hour of good context along with the clutter. Too blunt.
The right tool here is its gentler cousin:
/compacttidies the desk instead of clearing it. Claude writes itself a short summary of what actually matters — the goal, the decisions, where things stand — sweeps away the bulky raw material, and keeps working on the same task with the thread intact.
So the two aren’t interchangeable; they’re for two different moments:
/clear— empty the desk. Fresh start, nothing carried over. For a poisoned conversation or a brand-new, unrelated task./compact— tidy the desk. Keep going on the same task, just with room to work again. For a long, healthy session that’s running out of space.
The thing that trips people up
The instinct, when Claude starts dropping details, is to read it as Claude got dumb — and then to fight it: repeat the instruction louder, re-paste the file, get frustrated, or /clear and lose the hour you just invested. None of that addresses the actual problem, because the problem isn’t Claude’s intelligence. It’s desk space.
The tell is the timing. If Claude felt sharp early and started slipping only after a long, full session, that’s a full desk, not a bad model. /compact and carry on. (Claude will often nudge you toward this on its own when the window gets tight — but now you know what it means and don’t have to wait to be asked.)
What’s next
You can spot a big task, plan it, slice it, steer it, restart it when it sours, and now keep it from drowning in its own context. The last lesson puts every one of those moves together on a single real, end-to-end task — so you can see how the whole workflow actually flows.