[FEATURE] `/new` should support an `[session name]` argument, saving extra `/rename`
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 pretty frequently run /new then /rename [session name] as a sequence, to organize my sessions.
This is especially needed given that auto-naming is not reliable nor programmatic, as reported in https://github.com/anthropics/claude-code/issues/74313 (among other issues)
Proposed Solution
I think a simple fix to this would be allowing /new to accept an optional session name argument, saving the extra /rename step. This occurred to me when I attempted to do this, and realized it wasn't already supported.
Alternative Solutions
The risk here might be if the /new//clear behavior is not coupled to the session name, but it is as far as I can tell (running either will clear the session name as well)
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
_No response_
Additional Context
Please tell me if this is not the no-brainer UX improvement that I suspect it is. Thanks in advance!
For context, I did a cursory search of other issue proposals, many around auto/programmatic session naming: https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement%20%22%2Fnew%22%20%22%2Frename%22