You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] Add descriptive titles for continued sessions after context limit #12613
I have searched existing requests and this feature hasn't been requested yet
This is a single feature request (not multiple features)
Problem Statement
When a conversation hits the context limit, a new session starts with the message "This session is being continued from a previous conversation that ran out of context." However, the new session gets an auto-generated title based on the first message rather than a meaningful title that reflects it's a continuation.
This makes it difficult to:
Find the right conversation thread when you have multiple sessions
Understand which continuation belongs to which original session
Navigate between related sessions that are part of the same task
Proposed Solution
When continuing a session due to context limits, automatically generate a title that:
Indicates it's a continuation (e.g., "Continued: [original topic]")
Carries context from the previous session's topic
Helps users identify which conversation thread they're in
For example:
Original session: "Implementing user authentication"
Continued session: "Continued: Implementing user authentication"
Alternative Solutions
Currently I work around this by manually renaming conversations (if that's possible) or keeping track of which sessions are related in a separate note. Other tools handle this by either:
Showing a visual link between related sessions
Auto-generating numbered continuations (Part 1, Part 2, etc.)
Priority
Medium - Would be very helpful
This doesn't block work but significantly impacts session management and organization when working on long tasks.
Feature Category
Interactive mode (TUI)
Use Case Example
Example scenario:
I'm debugging a complex issue that requires reading many files and making multiple changes
The conversation hits the context limit after 2 hours of work
A new session starts but has a generic title like "Continue previous conversation"
I now have 3-4 continued sessions open and can't tell which is which
With descriptive titles, each would clearly show what task they're related to
This would save time navigating between sessions and reduce confusion
Additional Context
This becomes especially important for:
Long-running development tasks that span multiple sessions
Users who keep multiple conversation threads open
Team environments where people might need to reference specific sessions
changed the title [-]Add descriptive titles for continued sessions after context limit[/-][+][feature] Add descriptive titles for continued sessions after context limit[/+]on Nov 28, 2025
changed the title [-][feature] Add descriptive titles for continued sessions after context limit[/-][+][FEATURE] Add descriptive titles for continued sessions after context limit[/+]on Nov 28, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
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.
Activity
[-]Add descriptive titles for continued sessions after context limit[/-][+][feature] Add descriptive titles for continued sessions after context limit[/+][-][feature] Add descriptive titles for continued sessions after context limit[/-][+][FEATURE] Add descriptive titles for continued sessions after context limit[/+]github-actions commentedon Nov 28, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Dec 29, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
github-actions commentedon Jan 28, 2026
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
github-actions commentedon Feb 4, 2026
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.