Auto-naming sessions stopped working around v2.1.60+

[sgtowns]

Description

Session auto-naming (where Claude Code automatically generates a descriptive session name based on conversation content) stopped working approximately 3 days ago (around Feb 25, 2026). Previously, sessions would get renamed automatically every few minutes as the conversation topic evolved. Now sessions remain unnamed unless manually using /rename.

Environment

• Claude Code version: 2.1.63
• OS: macOS (Darwin 25.3.0)
• Model: Claude Opus 4.6

Steps to reproduce

1. Start a new Claude Code session
2. Have a multi-turn conversation with a clear topic
3. Observe that the session never gets auto-named

Expected behavior

Sessions should automatically receive descriptive names based on conversation content, as they did prior to ~Feb 25.

Actual behavior

Sessions remain unnamed. /rename without arguments works (generates a name from context), but the automatic/periodic renaming no longer fires.

Related issues

• [BUG] Renamed session works on first resume but the name disappears after the second exit #25090 — Renamed session name disappears after second exit
• Session name set by /rename is overwritten after /resume #23610 — /rename overwritten after /resume
• Auto-name sessions based on first message #24672 / Feature: Auto-generate descriptive session names #22896 — Auto-name sessions feature tracking

[github-actions]

Found 2 possible duplicate issues:

1. Sessions-index.json: summaries not generated and new sessions not indexed since ~v2.1.31 #24729
2. Terminal tab title shows static 'claude code' instead of conversation topic #28983

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.