checkpoint

Save and restore Claude Code conversation context as markdown checkpoints.

5|1|Updated Apr 4, 2026

Search Tags:#context management #checkpoint #claude-code #command automation #session restore #jsonl extraction

Ready to run

npx skills add https://github.com/sinzin91/claude-checkpoint --skill checkpoint-sinzin91

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It solves the problem of losing important decisions, corrections, and working context when you run /clear and must start over in Claude Code.

Core Features & Use Cases

Session checkpointing: Runs /checkpoint to extract the last N human/assistant messages into a structured markdown checkpoint file in /tmp.
Structured summaries for fast re-entry: Provides a Summary section that you (Claude) fill with goal, decisions, files modified, corrections, patterns, blockers, and the literal next step.
Reliable restoration: Uses /restore to read the checkpoint back and continue the conversation without re-summarizing or acknowledging the restoration.

Quick Start

Ask Claude to run /checkpoint before you run /clear, then ask Claude to run /restore after /clear to continue exactly where you left off.

Frequently Asked Questions about checkpoint

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

FAQPage Schema

How do I save Claude Code session context before running /clear?▼

You preserve Claude Code session context before /clear by running /checkpoint, which extracts recent JSONL conversation messages into a structured markdown file containing a summary of goals, decisions, and next steps.

Can I restore a Claude Code conversation after clearing the context window?▼

Yes, you can restore a Claude Code conversation after clearing the context window by running the /restore command, which reads the checkpoint file back and continues the session without re-summarizing or acknowledging the restoration.

What is the best way to prevent losing decisions and working state in Claude Code?▼

The best way to prevent losing decisions and working state in Claude Code is applying a checkpoint before context limits force a reset, which extracts session messages into a structured markdown summary capturing goals, decisions, and blockers.

Does Claude Code session checkpointing require external network access or dependencies?▼

No, Claude Code session checkpointing requires no external network access or dependencies. It operates locally by extracting JSONL session messages into markdown checkpoint files written to the /tmp directory.

How do I restore a Claude Code session from a specific checkpoint file path?▼

To restore a Claude Code session from a specific checkpoint file path, use the /restore command with the target file path to rehydrate the structured markdown summary and continue the conversation exactly where you left off.

What information is included in a Claude Code checkpoint summary?▼

A Claude Code checkpoint summary includes the session goal, decisions made, files modified, corrections, established patterns, current blockers, and the literal next step required to resume the working state.