How it works

Local files become the next agent's starting point.

Checkpoint reads project memory from your checkout, selects the useful pieces, and prints a focused continuation pack you can inspect before sharing.

1. Create readable memory

checkpoint init creates a .contextos/ directory in the project. The directory is ordinary text: context, tasks, handoffs, decisions, and lightweight state. 

.contextos/
  context/
    constraints.md
  tasks/
    active/
  handoffs/
    latest.md
  decisions/
  state/

2. Capture the handoff

Before switching tools, leave the status in a handoff: what changed, what was verified, what is blocked, and what should happen first in the next session. 

# Handoff

## Current status
Source install works in a fresh checkout.

## Verified
- checkpoint --help
- checkpoint init

## Next action
Improve the empty-project recovery message.

3. Generate projections

Checkpoint can write agent-facing project files such as AGENTS.md or CLAUDE.md from the same source material. The output stays readable, so you can review the projection before it guides another tool.

.contextos/ to AGENTS.md and CLAUDE.md

4. Print a continuation pack

checkpoint continue gathers the current task, recent handoff, project constraints, and target agent into a compact Markdown prompt. 

checkpoint continue --from codex --for claude-code

5. Inspect, then paste

The continuation pack is meant to be read by a human before use. Edit the source files, regenerate the pack, or paste only the parts that fit the next session.