Agent Checkpoint — Documentation skill for Claude Code
Repo-local checkpoint and resume skills for coding agents.
How to install Agent Checkpoint
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open hotalexnet/agent-checkpoint and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Agent Checkpoint does
Repo-local checkpoint and resume skills for coding agents. Handoffs are plain markdown under .agents/checkpoints/, so Codex can write one and Claude Code or opencode can pick it up later — across sessions, machines, and model switches.
Alternatives in Documentation
- 会话管理(Session Manager)需求文档(PRD / Markdown) — 目标:对 Codex / Claude Code 的本地会话记录进行可视化管理,并提供“一键复制 / 一键终端恢复”能力 31.7k ★
- Qmd Skill — A Codex/Clawd skill definition for qmd (Quick Markdown Search) 673 ★
- Cog — 240+ Cognitive architecture for Claude Code -- persistent memory, self-reflection, and foresight via plain-tex 294 ★
README
agent-checkpoint
[](https://opensource.org/licenses/MIT) [](https://www.python.org/) [](#how-it-works) **English** | [**中文**](./README.zh-CN.md)
Repo-local continuity skills for coding agents. Checkpoints use a shared `agent-handoff/v1` markdown format so Codex/OpenAI CLI, Claude Code, opencode, and other programming agents can write and resume the same repo state.
These two skills turn "I lost the thread" into a recoverable workflow: save the real working lane into the repository itself, then restore it in the next session without depending on fragile external chat memory.
Demo

What It Does
- repo-checkpoint — writes a timestamped markdown handoff under
.agents/checkpoints/, including session goal, current state, key chat context, files in play, verification state, next step, and a git snapshot. - repo-resume — restores the latest active lane from the newest checkpoint plus current branch, working tree, and recent commits.
**Why this exists:** Most agents can reread code. What they usually lose is the human context: what the user actually wanted, what was already tried, which constraints mattered, and what the next concrete step should be.
Why It Matters
- Repo-local, not session-local — the handoff lives inside the repo, so it survives model switches, browser restarts, shell reconnects, and machine changes.
- Cross-agent by design — Codex can write a checkpoint and Claude Code or
opencode can resume it later from the same
.agents/checkpoints/directory. - Plain markdown, no lock-in — checkpoints are readable in any editor and reviewable in git.
- Fast cold start — resume goes straight to the last known lane instead
Related Skills
Agent Memory Kit
One memory for every coding agent — plain markdown in your repo. Injected on Claude Code & Cursor, skills on C
StickyMD
Native sticky notes for GNOME X11, kept behind regular windows and stored as plain Markdown that Codex, Claude
Observational Memory
Local-first shared memory for Claude Code, Codex, OpenCode, Kimi, Grok, Cowork, and Hermes, with bounded obser
Crewplane
Run reviewable, resumable coding-agent workflows across Claude Code, Codex, Gemini, GitHub Copilot CLI, or any
Baton
Baton — clean session handoffs: pass in-progress work to the next agent with a single verified markdown file.
Cairn
Turn a markdown plan document into a graph of verified, concurrent coding-agent work — committed-marker resume
Related Agents
Agent Of Empires
Claude Code, OpenCode, Mistral Vibe, Codex CLI, Gemini CLI Coding Agent Terminal Session manager via tmux and
Developer Overview
code-container (container) creates isolated Docker environments for AI coding harnesses (Claude Code, OpenCode
Ferrox Debug Session Manager
Manages multi-cycle /ferrox:debug checkpoint and continuation loop in isolated context. Spawns ferrox-debugger