Rename Sessions Before You Drown
Sessions survive restarts — nothing burns when you close the app. But by default each is named after your first prompt, and in a week you're squinting at twenty identical grey lines. Two seconds of renaming per session buys you instant recall.
Why it works
Sessions survive restarts — nothing burns when you close the app — but by default each one is named after your first prompt, and in a week the sidebar is twenty grey lines of 'make me a landing…'. Two seconds of renaming per session is the cheapest organization system you will ever run, and future-you cashes the cheque daily.
How to do it
- Finish a block of work; click the session title at the top.
- Rename it by OUTCOME, not by request: 'invoice-bot v1', 'landing — pricing test'.
- Keep one task per session, so the name can stay honest.
- Use the sidebar filters when the list grows anyway.
- Archive sessions for shipped work — out of sight, still recoverable.
- Tomorrow: click the named session and continue exactly where you stopped.
Copy this
prompt
Summarize this session in one line I can use as its title: the thing built, its current state, and what's next. Max 8 words.
What to watch for
- Renaming 'later' means never — twenty unnamed sessions is the default outcome, not the exception.
- Don't fork one sprawling session for everything; names can't save a session that's secretly four projects.
Sources
Original: conon.aiDocumentation: code.claude.com