How do I install the Restore skill?

Run npx skillmds@latest add motlin/restore-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Restore safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Restore?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Restore free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Restore?

motlin (@motlin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Restore by motlin — Agent Skill

Name: Restore
Rating: 4.666666666666667 (3 reviews)
Author: motlin

Restore

Restore claude/codex agents from a resume-after-reboot JSON state file after tmux-resurrect reopens their windows. Use after a reboot when asked to restore, resume, or bring back tmux agents. For herdr instead of tmux, use the herdr-reboot plugin.

motlin Updated Sep 22, 2026

File contents

Restore Tmux Agents

After a reboot, tmux-resurrect reopens the windows and working directories. Resume the agents that were running in them from the JSON snapshot written by /tmux-reboot:snapshot.

Preview the plan first:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/restore.py .llm/resume-after-reboot-state.json

Show the user the list of windows and resume commands. Once they confirm, fire them:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/restore.py .llm/resume-after-reboot-state.json --go

The state file is JSON, schema resume-after-reboot/v1. A file written with any other schema value is rejected rather than guessed at, including the nested resume-after-reboot/v2 that herdr-reboot writes — its workspaces, tabs, and splits have no tmux equivalent here. The header line of the output echoes the backend and captured time so the user can see which plugin wrote the file and how stale it is.

Rows are paired with live windows by cwd, not by position, because tmux-resurrect renumbers windows. A row's slot is just a 1-based ordinal — pass --skip SLOT (repeatable) to leave one row alone. The window running the script is fired last so the restore is not interrupted mid-run. Each command is sent with a trailing Enter, so the user does not press return themselves — the script both pastes and runs every resume line.

Rows with "tool": "shell" are idle panes with no command; they are skipped. Alongside claude/codex agents, the snapshot may hold command rows — dev servers and watchers like just dev (restore_default: false), and read-only viewers like git log, less FILE, or htop (restore_default: true). This restore re-runs both the same way, unlike herdr-reboot, which fires only the viewers unless asked. Point the dev-server rows out before firing, since re-running one rebinds its port. Viewers re-run from the top: scroll position and search are not restored.

Rows are only fired into windows sitting idle at a shell prompt with no live agent, so a repeated run never types into a running program. Report the skipped rows to the user; "no live window with this cwd" usually means tmux-resurrect has not finished restoring, or that pane's window is gone.

Verify rows whose session_id is null and whose command is claude --continue or codex resume --last; those fallbacks mean the snapshot could not match an exact transcript. If a resumed session opens the wrong conversation because one working directory held multiple agents or an idle Codex transcript had a stale modification time, run codex resume or claude --resume manually in that window and use the interactive picker.

---name: restore-2description: Restore claude/codex agents from a resume-after-reboot JSON state file after tmux-resurrect reopens their windows. Use after a reboot when asked to restore, resume, or bring back tmux agents. For herdr instead of tmux, use the herdr-reboot plugin.---# Restore Tmux AgentsAfter a reboot, tmux-resurrect reopens the windows and working directories. Resume the agents thatwere running in them from the JSON snapshot written by `/tmux-reboot:snapshot`.Preview the plan first:```bashpython3 ${CLAUDE_PLUGIN_ROOT}/scripts/restore.py .llm/resume-after-reboot-state.json```Show the user the list of windows and resume commands. Once they confirm, fire them:```bashpython3 ${CLAUDE_PLUGIN_ROOT}/scripts/restore.py .llm/resume-after-reboot-state.json --go```The state file is JSON, schema `resume-after-reboot/v1`. A file written with any other `schema`value is rejected rather than guessed at, including the nested `resume-after-reboot/v2` that`herdr-reboot` writes — its workspaces, tabs, and splits have no tmux equivalent here. The headerline of theoutput echoes the `backend` and `captured` time so the user can see which plugin wrote the file andhow stale it is.Rows are paired with live windows by `cwd`, not by position, because tmux-resurrect renumberswindows. A row's `slot` is just a 1-based ordinal — pass `--skip SLOT` (repeatable) to leave onerow alone. The window running the script is fired last so the restore is not interrupted mid-run.Each command is sent with a trailing Enter, so the user does not press return themselves — thescript both pastes and runs every resume line.Rows with `"tool": "shell"` are idle panes with no command; they are skipped. Alongside`claude`/`codex` agents, the snapshot may hold `command` rows — dev servers and watchers like`just dev` (`restore_default: false`), and read-only viewers like `git log`, `less FILE`, or`htop` (`restore_default: true`). This restore re-runs both the same way, unlike `herdr-reboot`,which fires only the viewers unless asked. Point the dev-server rows out before firing, sincere-running one rebinds its port. Viewers re-run from the top: scroll position and search are notrestored.Rows are only fired into windows sitting idle at a shell prompt with no live agent, so a repeatedrun never types into a running program. Report the skipped rows to the user; "no live window withthis cwd" usually means tmux-resurrect has not finished restoring, or that pane's window is gone.Verify rows whose `session_id` is `null` and whose command is `claude --continue` or`codex resume --last`; those fallbacks mean the snapshot could not match an exact transcript. If aresumed session opens the wrong conversation because one working directory held multiple agents oran idle Codex transcript had a stale modification time, run `codex resume` or `claude --resume`manually in that window and use the interactive picker.

Frequently asked questions