Skip to content

Allow renaming conversation titles in Past Conversations #11956

Closed

Description

@reiku29

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

Currently, there is no way to rename or customize conversation titles in the "Past Conversations" section of Claude Code. Users are limited to auto-generated titles, which makes it difficult to organize and quickly identify specific conversations when working on multiple projects or tasks.

Proposed Solution

Add a rename/edit functionality for conversation titles in the "Past Conversations" list. This could be implemented through:

  • A right-click context menu with a "Rename" option
  • An edit icon that appears on hover next to each conversation title
  • Double-click on the conversation title to enter edit mode

The workflow would be:

  • User triggers the rename action
  • Conversation title becomes editable (inline text field)
  • User types the new custom name
  • User presses Enter or clicks outside to save
  • The new title is persisted and displayed in the list

Alternative Solutions

  1. Auto-tagging system: Automatically extract keywords from conversations and allow users to filter by tags
  2. Folder/category organization: Allow users to organize conversations into custom folders or categories
  3. Search-only approach: Enhance the search functionality to find conversations by content instead of relying on titles
  4. Prefix/suffix customization: Allow users to add custom prefixes or suffixes to auto-generated titles

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

I'm currently working with legal resolution documents (e.g., "resolucion 1843 de 2025", "resolucion 1888 de 2025"). Being able to rename my conversations to match the document names would allow me to:

  • Quickly identify which conversation relates to which resolution
  • Maintain better organization across multiple document reviews
  • Resume work on specific resolutions without having to open and check multiple conversations
  • Keep a clear historical record of work done on each document

Additional Context

This feature would be particularly valuable for:

  • Users managing multiple client projects
  • Developers working on different features simultaneously
  • Teams using Claude Code for code reviews with specific PR numbers or ticket IDs
  • Anyone who needs to reference previous conversations regularly

Similar features exist in other AI chat interfaces and have proven to be essential for productivity and organization.

Activity

  1. github-actions commented on Nov 19, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. Rename the conversation #7441
    2. Add ability to name and organize conversation sessions #11408
    3. [Feature Request] Add --session-name and /session-name for custom session identification #2112

    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

  2. reiku29 commented on Nov 19, 2025

    @reiku29
    Author

    Its True! Close

  3. github-actions commented on Nov 27, 2025

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

  4. locked as resolved and limited conversation to collaborators on Nov 27, 2025
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

    area:tuiduplicateThis issue or pull request already existsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions