claude-code - 💡(How to fix) Fix Allow --resume to accept session name as an alternative to UUID [2 comments, 3 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#54796Fetched 2026-04-30 06:35:45
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Timeline (top)
commented ×2labeled ×2cross-referenced ×1

Allow claude --resume <name> to work as an alternative to claude --resume <uuid>, using the session name set via /rename.

Root Cause

Allow claude --resume <name> to work as an alternative to claude --resume <uuid>, using the session name set via /rename.

Fix Action

Fix / Workaround

A simple workaround is a shell function that greps the .jsonl files for the title, but this should be a built-in capability given that naming is already a first-class feature.

Code Example

claude --resume lte-dvt-procedure

---

claude --resume bfba5447-39eb-4980-a341-dab9b4566da8
RAW_BUFFERClick to expand / collapse

Feature Request

Summary

Allow claude --resume <name> to work as an alternative to claude --resume <uuid>, using the session name set via /rename.

Current behavior

  • Sessions can be named via /rename <name>, but the name is only a display label.
  • --resume only accepts a UUID.
  • --continue resumes the most recent session with no way to specify which one.
  • There is no way to resume a session by name from the CLI.

Desired behavior

claude --resume lte-dvt-procedure

Should resolve the session name to its UUID and resume it, equivalent to:

claude --resume bfba5447-39eb-4980-a341-dab9b4566da8

Why

Session names are already supported via /rename and shown in --list. Supporting name-based resume would make it much easier to return to long-running or named work sessions without having to look up or remember UUIDs.

A simple workaround is a shell function that greps the .jsonl files for the title, but this should be a built-in capability given that naming is already a first-class feature.

Suggested implementation

When --resume <arg> is passed and <arg> is not a valid UUID, fall back to searching session files for a matching title and resume the most recent match.

extent analysis

TL;DR

Modify the --resume command to accept session names by falling back to a search for a matching title in session files when the provided argument is not a valid UUID.

Guidance

  • Check if the session name is correctly set via the /rename command and verify it is displayed in the --list output.
  • Consider implementing a fallback mechanism in the --resume command to search for a matching session title when a non-UUID argument is provided.
  • To mitigate the current limitation, a temporary workaround could be to use a shell function that greps the .jsonl files for the title, as mentioned in the issue.
  • Verify the proposed solution by testing the --resume command with both valid UUIDs and session names.

Example

# Proposed implementation in pseudocode
if ! is_uuid(arg):
  session_id = find_session_by_title(arg)
  if session_id:
    resume_session(session_id)
  else:
    print("Session not found")

Notes

The suggested implementation relies on the assumption that session names are unique. If there are duplicate session names, the fallback mechanism may need to be adjusted to handle this case.

Recommendation

Apply workaround: Implement the fallback mechanism in the --resume command to support resuming sessions by name, as it provides a more user-friendly experience and leverages existing 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 Allow --resume to accept session name as an alternative to UUID [2 comments, 3 participants]