claude-code - 💡(How to fix) Fix Add ability to rename sessions for --resume [2 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#49200Fetched 2026-04-17 08:48:03
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2closed ×1

Common workflow: paste a Slack/GitHub URL as the first message, then do extensive work. The session becomes impossible to find later in --resume without trial and error.

Error Message

Common workflow: paste a Slack/GitHub URL as the first message, then do extensive work. The session becomes impossible to find later in --resume without trial and error.

Root Cause

Common workflow: paste a Slack/GitHub URL as the first message, then do extensive work. The session becomes impossible to find later in --resume without trial and error.

Fix Action

Fix / Workaround

Current workaround

RAW_BUFFERClick to expand / collapse

Problem

When resuming sessions with claude --resume, sessions are identified by their first user message. If that message is a URL (e.g. a Slack link) or otherwise non-descriptive, there's no way to identify the session later.

There's no built-in command to rename/retitle a session.

Expected behavior

A command like /title <name> or /rename <name> that sets a human-readable title for the current session, displayed in the --resume picker.

Current workaround

None — you just have to remember which cryptic first message corresponds to which task.

Context

Common workflow: paste a Slack/GitHub URL as the first message, then do extensive work. The session becomes impossible to find later in --resume without trial and error.

extent analysis

TL;DR

Implementing a /title or /rename command to set a human-readable title for sessions would likely resolve the issue.

Guidance

  • Introduce a new command, such as /title or /rename, that allows users to set a descriptive title for their sessions.
  • Store the title along with the session data to display it in the --resume picker.
  • Consider validating the title input to ensure it's descriptive and not empty.
  • Update the --resume picker to display the session title instead of the first message.

Example

# Example usage of the proposed /title command
claude --session-id <id> /title "My Descriptive Session Title"

Notes

The implementation details of the /title command and session data storage are not specified, so the above guidance is high-level.

Recommendation

Apply workaround: Implement the proposed /title or /rename command to improve session identification and management. This approach directly addresses the reported issue and provides a clear solution.

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…

FAQ

Expected behavior

A command like /title <name> or /rename <name> that sets a human-readable title for the current session, displayed in the --resume picker.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING