26 lines
1.4 KiB
Markdown
26 lines
1.4 KiB
Markdown
---
|
|
name: recover
|
|
description: >
|
|
Reconstruct a session log from a crashed or unsaved session transcript (Claude Code or Grok format). Use when the user says /recover, "recover the session", "reconstruct the log from the crash", "/recover latest", or provides a UUID.
|
|
---
|
|
|
|
# /recover — Session Recovery
|
|
|
|
Reconstruct a ClaudeTools session log from a driver transcript when the session ended before /save could run.
|
|
|
|
**Grok support:** We have added native support.
|
|
|
|
- For Claude Code transcripts: uses `.claude/scripts/recover_session.py`
|
|
- For Grok sessions: uses the new `.claude/scripts/recover_grok_session.py` (discovers `~/.grok/sessions/<slug>/<uuid>/`, extracts terminal logs, etc.)
|
|
|
|
See the updated `.claude/commands/recover.md` for usage, flows, and the Grok-specific section.
|
|
|
|
When this skill is invoked:
|
|
- Read `.claude/commands/recover.md` for the current dispatcher logic and examples.
|
|
- Use `run_terminal_command` to invoke the appropriate python script with --list / --latest / --uuid / --print / --auto.
|
|
- The output should be reviewed before writing (the scripts support --print for review).
|
|
- Adapt any sub-agent usage in the recovery process to Grok's `spawn_subagent`.
|
|
|
|
This is critical for continuity after crashes. The recovered log can then be committed via /checkpoint or /scc.
|
|
|
|
Full details on what gets extracted (verbatim commands/outputs vs. prose) and placement of the resulting .md are in the command doc and the two recover_*.py scripts. |