claude-code - 💡(How to fix) Fix Make /rename auto-generated session titles more descriptive (or configurable)

Summary

When /rename is invoked without arguments, the auto-generated session title is usually very short and generic (often just a few words that don't carry enough signal to distinguish sessions in /resume or the sessions list). I'd like the default output to either be richer by default, or to be configurable.

Why this matters

I run multiple parallel sessions (often background jobs) across the same repo. When I come back to /resume or scan the sessions picker, short titles like "fix bug" or "update file" don't help me pick the right one. I end up renaming manually almost every time, which defeats the purpose of the auto-generator.

Proposals (either would help)

A. Make the default more descriptive. Aim for 8-15 words and include concrete nouns from the conversation: the file/feature touched, the symptom of a bug being fixed, or the user-visible goal. Example of what I'd want:

• Current: "fix rename bug"
• Desired: "fix /rename losing session title after context compaction in VSCode"

B. Make the naming prompt configurable. Add a settings.json key, for example:

{
  "session": {
    "autoNamePrompt": "Summarize this session in 8-15 words. Include the primary file, feature, or symptom."
  }
}

This lets users with different workflows tune it without changing the binary, and keeps the default behavior unchanged for everyone else.

Context

• Checked claude --help for a relevant flag and didn't find one.
• Checked ~/.claude/settings.json schema and don't see a key that controls this.
• There's no user-facing skill or hook for /rename; the prompt appears to be internal to the CLI.

Happy to test either approach if it ships behind a flag.