Menu
Snapshot running tmux claude/codex agents immediately before a reboot so their sessions can be restored afterward.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Restore claude/codex agents from a tmux-reboot snapshot after tmux-resurrect reopens their windows.
Commit changes, run git-test precommit checks, and fix failures. Use when asked to fix build, test, lint, typecheck, or precommit failures.
Running precommit checks and build validation. ALWAYS use after ANY code changes.
This skill should be used after completing any task, before returning control to the user. Always run this skill โ it handles the case where there's nothing to do.
Coordination guidelines for leading a team of task-executing agents
Workflow guidelines for team members executing tasks
| name | snapshot |
| description | Snapshot running tmux claude/codex agents immediately before a reboot so their sessions can be restored afterward. |
Capture the current tmux session state to a snapshot file, so /tmux-reboot:restore can bring the
agents back after tmux-resurrect restores the windows, panes, and working directories. The running
claude and codex processes do not survive the reboot and must be resumed separately. Panes
running a long-lived foreground command (dev servers and watchers like just dev, npm run dev,
vite, cargo watch) are also captured as command rows โ these carry no session state, so
restoring one just re-runs the command line (best-effort).
Run:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/snapshot.py > .llm/resume-after-reboot-state.md
Then show the user the generated table and confirm it looks right before they reboot. The state file
holds session ids personal to this machine, so keep it in the gitignored .llm/ directory.
The script walks the process tree under each pane in the attached tmux session and matches the agent's working directory to recent transcripts on disk. Review these matching caveats with the user when they affect the generated table:
codex resume picker after reboot.claude --continue or codex resume --last.
Point out these fallback rows so the user knows to verify them after restoration.command rows re-run their command line, not a saved session. Editors, REPLs, and shells with
in-memory state (vim, psql, ssh) are intentionally not captured โ only allowlisted
long-running commands are. Point these rows out as best-effort restores.Regenerate immediately before rebooting so the session ids are current. Keep refresh manual unless the user asks to automate it with cron or launchd.