claude-code - 💡(How to fix) Fix [FEATURE] Allow custom titles for conversations shown in /resume [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52060Fetched 2026-04-23 07:37:36
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

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 using /resume to return to a past conversation, the list shows auto-generated titles (typically based on the last user message), which often makes it hard to identify what each conversation was actually about. I'd like a way to set or edit a custom title for a conversation.

Current behavior

  • Past conversations in /resume are labeled with what appears to be the most recent prompt or an auto-generated summary.
  • There is no user-facing command to rename or set a custom title.
  • When I have many past sessions, I often can't tell which one contains the work I'm looking for without opening several of them.

Desired behavior

Any of these would solve the problem:

  1. A slash command like /rename <title> to set a custom title for the current conversation.
  2. An option in /resume to edit the title of a listed conversation.
  3. A way to "pin" or tag a conversation with a descriptive label (e.g., ticket number, feature name).

Why this matters

  • I often work on multiple tickets/features in parallel and return to past sessions days later.
  • The current auto-title is frequently the last thing I said ("ok thanks", "let's try that"), which gives no context.
  • Branch names help narrow things down, but multiple conversations can happen on the same branch.

Example

Instead of seeing:

  • ok let's commit that
  • can you check the logs again
  • yes that looks right

I'd like to see:

  • Email subscription approval flow (#8054)
  • PDF restpack status code fix
  • Marketing user resolution refactor

Environment

  • Claude Code version:2.1.117
  • OS: Linux (WSL2) and Ubuntu

Proposed Solution

I'd suggest starting with option 1 (the simplest) and potentially expanding later:

Option 1 — /rename slash command (minimal)

Add a slash command that sets a custom title on the current conversation:

/rename Email subscription approval flow (#8054)

  • Stored as metadata alongside the conversation transcript.
  • If set, the custom title is shown in /resume instead of the auto-generated one.
  • Running /rename with no argument could clear it and revert to auto-title.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Implementing a /rename slash command to set custom titles for conversations would likely address the issue.

Guidance

  • Consider adding a new slash command, such as /rename, to allow users to set custom titles for conversations, which would be stored as metadata alongside the conversation transcript.
  • To verify the effectiveness of this solution, test the /rename command with various titles and ensure that the custom titles are displayed correctly in the /resume list.
  • When implementing the /rename command, consider adding an option to clear the custom title and revert to the auto-generated title, such as by running /rename with no argument.
  • Evaluate the potential impact of this feature on existing conversation management workflows and consider any necessary adjustments to ensure a seamless user experience.

Example

/rename Email subscription approval flow (#8054)

This example demonstrates how a user might use the proposed /rename command to set a custom title for a conversation.

Notes

The proposed solution focuses on implementing a /rename slash command, which may not address all possible use cases, such as editing titles in the /resume list or pinning conversations with descriptive labels. Further development may be necessary to fully meet the user's needs.

Recommendation

Apply workaround: Implement the proposed /rename slash command as a minimal solution to address the user's immediate needs, with the potential for future expansion to include additional features.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE] Allow custom titles for conversations shown in /resume [1 comments, 2 participants]