Skip to content

[FEATURE] Ability to set session summary from within the session #5846

Closed as not planned

Description

@MarcinOrlowski

I have tons of sessions, often for the same branch and at the same time etc and it's really painful for me to find the right one to resume as what -r is giving is auto-generated and (worse) artificially truncated to 60 chars or so. I'd love to be able to override the auto-generated session summary (say with /summary <WHATEVER> (with no length limit for <WHATEVER>) ) that then should stay immutable. While I do not seem much use case that myself, the /summary should most likely be accompanied by counter command to revert back to auto generated summary (i.e. /auto-summary).

Activity

  1. github-actions commented on Aug 15, 2025

    @github-actions

    Found 3 possible duplicate issues:

    1. [FRE] Support for custom "summary" field #3485
    2. [FEATURE REQUEST] Ability to add custom label to the Claude Code session #2194
    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. coygeek commented on Aug 17, 2025

    @coygeek

    Hey! As another user of Claude Code, I just wanted to say this is a fantastic feature request. I've definitely run into the same problem where my session list from claude --resume gets cluttered and it's tough to distinguish between different tasks, especially when working on the same branch.

    I took a look through the latest documentation to see if there was a hidden way to do this, and it looks like you're right—there isn't a direct command like /summary currently available. The docs confirm that the summary is auto-generated in the background based on the initial prompt and conversation.

    While it's not as good as your proposed solution, I have found a small workaround that might help in the meantime. Since the session summary is heavily influenced by the initial prompt, you can make your session names more descriptive by being very explicit when you first start claude.

    For example, instead of just starting with a simple task:

    claude "fix the button alignment on the profile page"

    You could start it with a clear, self-documenting "title":

    claude "SESSION: Fix profile button alignment (JIRA-451) and add responsive styles"

    The claude --resume list will then pick up this more descriptive initial prompt as the summary. It's not perfect, because as you noted, it still gets truncated. However, it at least makes the first ~60 characters much more meaningful and searchable.

    Your idea for a dedicated /summary command is definitely the ideal solution for better session management. It would be a huge quality-of-life improvement.

    Hopefully, the dev team sees this and considers it for a future release! Until then, I hope this little trick helps you navigate your sessions a bit more easily.

    Cheers

  3. github-actions commented on Dec 5, 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.

  4. github-actions commented on Jan 6, 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.

  5. github-actions commented on Jan 13, 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.

  6. locked as resolved and limited conversation to collaborators on Jan 13, 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

    area:corearea:tuiautocloseIssue will be closed automaticallyduplicateThis 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