named/tagged sessions would be a useful addition, especially for switching between projects or models.

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

> why it is claude --resume <some random number>? can't i name the session. so that i can maintain session model vice and resume them later when i work on specific model

Current limitations:

• No --name flag exists
• No built-in session labeling
• Sessions expire/get pruned over time

This is a known gap in Claude Code. You can request this feature at https://github.com/anthropics/claude-code/issues — named/tagged sessions would be a useful addition, especially for
switching between projects or models.

Proposed Solution

simple solution only. Just you missed the feature

Alternative Solutions

simple solution only. Just you missed the feature

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

I am working django web app having 5 app with 500 models. every app having CRUD and complex functions.
so every user used to separate/org files and folder according to models. the same way claude session should be arranged na?

Additional Context

_No response_