Feature request: Auto-name conversations after N tokens

Resolved 💬 2 comments Opened Mar 30, 2026 by faridjaff Closed Mar 30, 2026

Problem

When deep in a conversation, it's easy to forget to /rename it. Later, finding that conversation via claude -r becomes difficult since unnamed sessions only show by timestamp and first prompt.

Claude on the web (claude.ai) auto-names conversations after a few messages, making them easy to find later. Claude Code currently requires manually running /rename.

Proposed solution

Auto-generate a conversation name after a configurable token/message threshold (e.g., after 5k tokens or 3 messages). The name could be a short summary of the conversation topic, similar to how claude.ai handles it.

Ideally this would be configurable via settings:

  • Enable/disable auto-naming
  • Token or message threshold before triggering
  • Option to override with manual /rename

Why this matters

  • Conversations become searchable via claude -r <name> without extra effort
  • The conversation name shows in the status bar badge, giving context at a glance
  • Reduces friction for users who rely on conversation history

Additional context

We explored using hooks as a workaround, but hooks cannot run /rename and don't have access to whatever happens behind the scenes when /rename is executed. So this needs to be a first-party feature.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗