One Task, One Session
The agent re-reads the whole conversation with every message you send — side questions and dead ends ride along forever, degrading answers and burning limits. /clear is free; a cluttered context is not.
Why it works
The agent re-reads the entire conversation with every message you send — the side question about email subject lines rides along on every future turn of your landing-page task, degrading answers and burning limits. One task per session isn't tidiness; it's how you keep the context window filled with signal instead of sediment.
How to do it
- Finish a task? /clear before starting the next. It costs nothing.
- Unrelated question mid-task? Open a second session for it — don't contaminate this one.
- Big project? Slice it: design session, build session, polish session — staged like real work.
- Feel answers degrading? /context shows exactly what's occupying the window.
- Name each session for its one task (you're already renaming them, right?).
- End of day: close out with /clear rather than leaving a junk-drawer session for tomorrow.
Copy this
prompt
/clear
What to watch for
- One eternal mega-session 'so it remembers everything' achieves the opposite — the window fills, auto-compaction guesses at what mattered, and it remembers less.
- Project knowledge that must persist belongs in CLAUDE.md, not in conversation history — history is the wrong place to store anything.
Sources
Original: conon.aiDocumentation: code.claude.com