Skip to content

[FEATURE] Add descriptive titles for continued sessions after context limit #12613

Closed as not planned

Description

@guicheffer

Preflight Checklist

  • 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:

  1. I'm debugging a complex issue that requires reading many files and making multiple changes
  2. The conversation hits the context limit after 2 hours of work
  3. A new session starts but has a generic title like "Continue previous conversation"
  4. I now have 3-4 continued sessions open and can't tell which is which
  5. With descriptive titles, each would clearly show what task they're related to
  6. 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

Activity

  1. 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
  2. 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
  3. github-actions commented on Nov 28, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [FEATURE] --resume: Useful descriptions for sessions "continued from a previous conversation that ran out of context" #11367
    2. [BUG] The summary for resumed / compacted convesations is always "This session is being continued from a previo…" [sic] #8094
    3. Improve /resume conversation identification with context-aware labels #6455

    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

  4. github-actions commented on Dec 29, 2025

    @github-actions

    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.

  5. github-actions commented on Jan 28, 2026

    @github-actions

    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.

  6. github-actions commented on Feb 4, 2026

    @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.

  7. locked as resolved and limited conversation to collaborators on Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    autocloseIssue will be closed automatically

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions