🌐 English | 한국어 | 日本語 | 中文

Save and restore Claude Code sessions across devices. Never lose your work context again.

If this plugin saved your time, consider giving it a star.

Claude Code stores session history locally in ~/.claude/sessions/. This creates two problems:

1. Cross-device: When you switch computers, your context is gone
2. Reliability: Even on the same device, claude --continue and --resume depend on local session files that can become stale, corrupted, or lost after updates — leaving you to re-explain everything from scratch

session-saver does not depend on local session history. It saves your entire work context as git-committed files and generates a project-local /resume-{folder} command that auto-pulls and restores everything.

Note: Plugin skills are namespaced as /plugin-name:skill-name per Claude Code convention. The resume command is generated as a project-local skill, so it uses the short /resume-{folder} form.

Requires Claude Code v1.0.33 or later.

Paste the following prompt into Claude Code — it will automatically install the plugin while preserving your existing settings:

Add the following to ~/.claude/settings.json without removing any existing settings:

In enabledPlugins:
  "session-saver@claude-session-tools": true

In extraKnownMarketplaces:
  "claude-session-tools": { "source": { "source": "github", "repo": "thingineeer/claude-session-tools" } }

/plugins → Add marketplace → thingineeer/claude-session-tools → Install session-saver

Restart Claude Code after installation. That's it.

/session-saver:save-session

This will:

1. Commit all pending changes (split by logical unit)
2. Clean up worktrees and auto memory
3. Create docs/checkpoints/SESSION-STATE.md with full context
4. Generate .claude/skills/resume-{folder}/SKILL.md for the project
5. Push everything to remote

/resume-{folder-name}

This will:

1. git fetch — if behind remote, auto git pull
2. Read CLAUDE.md and SESSION-STATE.md
3. Read key files listed in the save point
4. Print a briefing with branch, progress, and next steps

No need to manually git pull. The resume command handles it.

Device A                                    Device B
  |                                           |
  |-- /session-saver:save-session             |
  |     |-- commit changes                    |
  |     |-- write SESSION-STATE.md            |
  |     |-- generate /resume-{folder} skill   |
  |     |-- push                              |
  |                                           |
  |              git push ────────>           |
  |                                           |
  |                                           |-- /resume-{folder}
  |                                           |     |-- git fetch + auto pull
  |                                           |     |-- read CLAUDE.md
  |                                           |     |-- read SESSION-STATE.md
  |                                           |     |-- read key files
  |                                           |     |-- print briefing

• Session conversation history (stays local)
• Secrets, credentials, .env files (excluded by design)
• Auto-generated files (node_modules/, Derived/, build/)

If you used v1.0.x, the resume command was generated as .claude/commands/resume-{folder}.md. Starting from v1.1.0, it is generated as .claude/skills/resume-{folder}/SKILL.md instead.

Running /session-saver:save-session on a project with an old-style command will automatically migrate it to the new skill format and delete the legacy command file.

Fork this repository and modify plugins/session-saver/skills/save-session/SKILL.md to fit your workflow:

• Change the SESSION-STATE.md template
• Add project-specific build verification steps
• Adjust commit message conventions

Contributions are welcome! Please open an issue or submit a pull request.

1. Fork the repository
2. Create a feature branch (git checkout -b feat/my-feature)
3. Commit your changes using Conventional Commits
4. Push to the branch and open a Pull Request

MIT