Skip to content

feat(launch): show session id prefix in resume picker#16

Merged
Tanq16 merged 2 commits into
Tanq16:mainfrom
rsridhr:resume-session-id
Jul 19, 2026
Merged

feat(launch): show session id prefix in resume picker#16
Tanq16 merged 2 commits into
Tanq16:mainfrom
rsridhr:resume-session-id

Conversation

@rsridhr

@rsridhr rsridhr commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

What

The launch --resume picker lists a project's sessions by first message + timestamp (+ account path when multiple accounts exist), but never shows the session id. Since --session <id> needs that id and each row otherwise looks similar, there was no way to tell which session a row maps to.

This prepends the 8-char session-id prefix to each row label:

a7f36f7f  Refactor the auth middleware       Jul 17 10:18pm  ~/.claude2
1b2c3d4e  Investigate flaky CI test          Jul 17 10:18pm  ~/.claude
5f6a7b8c  Draft release notes for v2         Jul 17 10:17pm  ~/.claude2

Details

  • Scoped to the interactive picker only (the default: branch in runLaunch). The --session <id>, --resume, and single-session fast paths are untouched.
  • Selection still resumes by the full internal sess.sessionID; the prefix is display-only.
  • Added a small shortSessionID helper (safe byte-slice — session ids are ASCII UUIDs).

Testing

  • gofmt / go vet / go build ./... clean, go test ./... passes.
  • Verified manually with multiple sessions across two accounts (~/.claude, ~/.claude2) — the id prefix renders correctly and selection resumes the right session.

🤖 Generated with Claude Code

The resume picker listed sessions by first message + timestamp only,
with no way to tell which session id each row maps to. Prepend the
8-char session id prefix to each row label so sessions are
identifiable at a glance.
Comment thread cmd/launch.go Outdated
@Tanq16
Tanq16 merged commit d783ccf into Tanq16:main Jul 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants