-
Notifications
You must be signed in to change notification settings - Fork 33
Description
Summary
happier --resume <happier-session-id> fails because the Happier session ID (e.g. cmmqnkplogx6ls93czcb78cl1) is passed directly to Claude Code's --resume, which only accepts UUIDs.
Steps to Reproduce
- Start a session:
happier --yolo - Note the Happier session ID from
happier daemon list(e.g.cmmqnkplogx6ls93czcb78cl1) - Try to resume:
happier --resume cmmqnkplogx6ls93czcb78cl1 --yolo
Result:
Error: --resume requires a valid session ID when used with --print.
Session IDs must be in UUID format (e.g., 550e8400-e29b-41d4-a716-446655440000).
Provided value "cmmqnkplogx6ls93czcb78cl1" is not a valid UUID
Exit code 1 from the Claude Code subprocess.
Expected Behavior
Happier should recognize its own session IDs and resolve them to the corresponding Claude Code UUID before passing --resume to Claude Code. The mapping already exists in session logs (the tag: field):
Session created/loaded: cmmqnkplogx6ls93czcb78cl1 (tag: 5f6bbc1b-41cc-4bda-8ef6-5115858b125a)
Workaround
Manually find the Claude UUID in the Happier logs and use that:
grep "tag:" ~/.happier/logs/*.log | grep <happier-session-id>
# then
happier --resume <claude-uuid> --yoloThis is painful and not discoverable.
Additional Context
happier daemon list only shows Happier session IDs, not Claude UUIDs. So the natural flow of "list sessions → pick one → resume it" is broken. Users have to dig through logs to find the UUID mapping.
🤖 Generated with Claude Code