[FEATURE] When a session auto-continues into a new conversation due to context limits, the new session should inherit the custom title.
Resolved 💬 3 comments Opened Feb 11, 2026 by arghorashy Closed Feb 15, 2026
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
If I name a conversation "My feature" and Claude eventually creates a new conversation because the context gets too big, the new conversation doesn't have a name. This means I get lost in my conversation histories when I come back the next day.
Proposed Solution
I'd expect that new conversation to carry over the name, e.g., "My feature (2)".
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
_No response_
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗