checkpoint

Save session state to .claude/state with optional MCP memory.

Updated Apr 15, 2026

Search Tags:#mcp #persistence #checkpoint #recovery #session #state #local-storage

Ready to run

npx skills add https://github.com/jasonmichaelbell78-creator/JASON-OS --skill checkpoint-jasonmichaelbell78-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/jasonmichaelbell78-creator/JASON-OS/tree/main/.claude/skills/checkpoint
Command: npx skills add https://github.com/jasonmichaelbell78-creator/JASON-OS --skill checkpoint-jasonmichaelbell78-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and restore session context to recover from failures or interruptions during long-running tasks.

Core Features & Use Cases

Local persistence: saves to .claude/state/ by default, enabling quick recovery after a crash.
MCP memory integration: optional --mcp to store session context in MCP memory for cross-session persistence.
Lightweight checkpoints: captures minimal viable state to resume tasks after restarts.

Use cases include continuing work after a terminal disconnect, recovering after a system crash, and ensuring resumption points across sessions.

Quick Start

Run /checkpoint to persist the current session state locally for recovery after failure.

Frequently Asked Questions about checkpoint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I save session state for recovery after a crash?▼

To save session state for recovery, run the checkpoint command to persist the current context locally. It writes handoff.json and per-task state files to the .claude/state directory, enabling a deterministic save-and-resume workflow after failures.

What is the best way to persist session context across multiple sessions?▼

Persisting session context across multiple sessions requires using the optional MCP memory integration. By enabling the --mcp flag, the session state is stored in MCP memory, allowing cross-session recovery and resumption points beyond local file persistence.

Does session checkpointing work with local file storage by default?▼

Session checkpointing works with local file storage by default, saving minimal viable state directly to the .claude/state/ directory. This enables quick recovery locally after a terminal disconnect or system crash without requiring external dependencies.

When do I need to save progress during long-running tasks?▼

You need to save progress during long-running tasks to prevent data loss from interruptions. Creating lightweight checkpoints captures the minimal viable state required to resume tasks seamlessly after unexpected restarts or terminal disconnects.

How do I resume a task after a terminal disconnect?▼

To resume a task after a terminal disconnect, rely on the previously saved checkpoint state. The skill captures minimal viable session context in local files, allowing you to recover your exact progress and continue the workflow deterministically.

Can I use MCP memory for cross-session state persistence?▼

You can use MCP memory for cross-session state persistence by enabling the optional --mcp flag. This stores the session context in MCP memory, extending recovery capabilities beyond the default local file storage for continuous workflows.