[BUG] /rename without arguments fails with "no conversation context yet" despite active conversation
Description
The /rename command's auto-generate feature (added in v2.1.41) fails with the error "Could not generate a name: no conversation context yet" even when called in a session with extensive conversation history.
Steps to reproduce
- Start a Claude Code session
- Have a multi-turn conversation (10+ exchanges including tool use and web searches)
- Run
/renamewithout arguments - Observe the error:
Could not generate a name: no conversation context yet. Usage: /rename <name> - Retry
/renamelater in the same session, same error persists
Expected behavior
/rename without arguments should auto-generate a descriptive session name based on the conversation context, as documented in the v2.1.41 changelog: "Improved /rename to auto-generate session name from conversation context when called without arguments."
Actual behavior
Every invocation returns: Could not generate a name: no conversation context yet. Usage: /rename <name>
The session clearly has context (extensive multi-turn conversation), so the "no conversation context yet" message is incorrect.
Environment
- Claude Code version: 2.1.45
- OS: macOS (Darwin 25.3.0)
- Shell: zsh
Additional context
- The feature was introduced in v2.1.41 per the changelog
- Issue #25455 confirms the auto-generate feature exists but docs haven't been updated
- Providing a name explicitly (
/rename my-name) works fine - Tested multiple times in the same session with the same result
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗