Rename Sessions Mid-Conversation with /rename
You don't have to name sessions before you start them. If a conversation turns out to be more useful than expected, rename it on the fly with /rename:
> /rename auth-refactor
The new name appears immediately in the prompt bar and your terminal title. It will also show up in the --resume picker the next time you want to return to this session:
claude --resume auth-refactor
This is handy when you start a session without a name and only realise mid-way that you'll want to return to it. Rather than trying to remember a UUID, just run /rename at the natural pause point before context gets lost.
It's also useful when juggling multiple windows — the terminal title updates immediately, so you can glance at your taskbar or tmux tab list and know which session is which without switching to it.
If you want to name sessions from the start instead, use the -n flag at launch:
claude -n "payment-integration"
/rename and -n both write to the same session metadata, so you can use either approach depending on whether you know the name upfront. The result is the same: a human-readable label in the --resume picker instead of a UUID.
Name or rename whenever the session becomes worth keeping — /rename takes two seconds and saves you hunting for UUIDs later.
Log in to leave a comment.
When typing feels slow — describing a complex bug, explaining architecture, or thinking through a problem out loud — press Option+V to switch to voice input. Speak naturally and Claude Code transcribes your words into a prompt, so you can describe what you need at the speed of thought.
When Claude is heading down the wrong path — editing the wrong file, writing code you don't want, or giving a long explanation you don't need — press Escape to stop it immediately. You keep everything it did up to that point and can redirect with a new prompt.
Closed a session and realized you weren't done? Pass --continue (or -c) when launching Claude Code to pick up exactly where you left off — same context, same files, same conversation history — without re-explaining what you were working on.