claude-code - 💡(How to fix) Fix /rename generates unusable /resume command [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#46371Fetched 2026-04-11 06:22:03
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

Code Example

Resume this session with:
claude --resume "Agents and Skills audit"

---

No conversations found to resume.
RAW_BUFFERClick to expand / collapse

Bug Description

After using /rename to give a session a display name, Claude Code prints:

Resume this session with:
claude --resume "Agents and Skills audit"

But running that exact command returns:

No conversations found to resume.

The same failure occurs with both claude --resume "name" from the shell and /resume "name" from within Claude Code.

Steps to Reproduce

  1. Start a Claude Code session
  2. Run /rename Agents and Skills audit
  3. Session header updates to show the new name
  4. Terminal prints Resume this session with: claude --resume "Agents and Skills audit"
  5. Exit the session
  6. Run claude --resume "Agents and Skills audit"
  7. Result: No conversations found to resume.

Expected Behavior

Either:

  • /resume should work with display names set by /rename, OR
  • The "Resume this session with:" line should show the actual session ID, not the display name

Actual Behavior

The generated resume command does not work. The tool instructs the user to run a command that fails.

Environment

  • Claude Code v2.1.100
  • Model: claude-sonnet-4-6
  • Platform: macOS (darwin)

extent analysis

TL;DR

  • The issue can be worked around by using the actual session ID instead of the display name set by /rename in the claude --resume command.

Guidance

  • Verify that the session ID is correctly stored or generated after renaming a session to ensure it can be resumed.
  • Check the documentation or source code of Claude Code to see if there's an option or command to retrieve the session ID after renaming.
  • Test resuming a session using the session ID directly in the claude --resume command to confirm it works as expected.
  • Consider filing a feature request or bug report to have the "Resume this session with:" message updated to use the session ID instead of the display name.

Example

  • No explicit code example is provided due to the lack of specific API or function details in the issue description.

Notes

  • The workaround assumes that the session ID is accessible or can be retrieved after a session is renamed.
  • The issue might be specific to the version of Claude Code (v2.1.100) or the model (claude-sonnet-4-6) being used.

Recommendation

  • Apply workaround: Use the actual session ID for resuming sessions until the issue is addressed in a future version of Claude Code, as it provides a reliable method to resume sessions despite the display name issue.

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