recover-session

Recover Session

Finds Claude Code sessions that have fallen off the /resume picker (the picker scopes to the current directory, but every transcript is on disk under ~/.claude/projects/), reconstructs context, and offers to relaunch.

Skill Directory

The skill's base directory is available as $SKILL_SCRIPTS_DIR (provided in the Base directory for this skill: header). The helper is at $SKILL_SCRIPTS_DIR/scripts/recover.js. It is read-only — it never edits or deletes transcripts.

Flow

1. Warn before showing any transcript content. Both the list output (intent) and the later summary are derived from transcript text, so print this prominently before running any command that displays session content:

   ⚠ Session transcripts can contain secrets or personal data. This summary is for your eyes — don't paste it into untrusted contexts.

   (The helper already strips tool_use/tool_result blocks, which is where credential output usually lives, but plain text turns can still contain sensitive material.)

2. Locate the session.

   • If the user gave a session id:

     node "$SKILL_SCRIPTS_DIR/scripts/recover.js" find <id>
     

     If that exits non-zero ("Session not found"), fall back to the no-id path below and help them pick.
   • If no id was given (or the id wasn't found):

     node "$SKILL_SCRIPTS_DIR/scripts/recover.js" list --limit 20
     

     Show the recent sessions (intent, cwd, time) and ask which one to recover, then run find <id> on their choice.

3. Summarize. From the turns in the find output, give a short reconstruction: the original intent (first user turn), the last user request, the last assistant action, and what looked like the next step.

4. Offer to relaunch. Give the user the command to resume in the original directory, for them to run themselves:

   cd "<cwd>" && claude --resume <id>
   

   Do not try to relaunch it in the background for them. Background relaunch can't be automated from here: /background only detaches a session a human is interactively attached to, so a spawned/detached process has no terminal to hand off and just ends up an orphaned TUI on an invisible PTY. Instead, tell the user that once the session is up they can type /bg (or /background) themselves to push it to the background.