[FEATURE] Naming session in Claude code

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I often run multiple Claude Code sessions in my terminal. If the terminal exits for any reason, I need to resume those sessions, but it becomes difficult to identify the correct one.

While I’m aware that sessions can be resumed using the session ID, I’m adapting to that approach—but it still feels inconvenient and not very user-friendly.

Proposed Solution

It would be very helpful if we could assign names to each Claude session. This would make it much easier to identify and resume sessions, instead of relying on session IDs.

For example:
claude --resume <session-name>

This would significantly improve usability when managing multiple sessions.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Example scenario: debugging a production issue across multiple Claude sessions

I often work on a live incident where I need several Claude Code sessions open at the same time — for example, one session to inspect logs, another to review deployment scripts, and another to draft a fix.

Here is how the flow usually looks:

1. I start a session to investigate the issue, but I do not finish the work in one sitting.
2. I open another Claude session later to compare outputs or test a different approach.
3. If my terminal closes unexpectedly, I have to resume the previous sessions manually.
4. At that point, I have to search through multiple session IDs, which is slow and easy to mix up.
5. If each session had a name like prod-incident-logs or db-migration-fix, I could resume the exact session immediately using something like:

claude --resume prod-incident-logs

This would save time, reduce confusion, and make it much easier to manage multiple ongoing tasks.

Additional Context

_No response_