Examples

Examples for real tool switches.

Each example uses fake project names and safe placeholder wording. Illustrative sample based on v0.1.0 behavior; verify exact output with checkpoint --help.

Claude to Codex

Use this when planning happened in Claude and implementation is moving into Codex. 

checkpoint continue --from claude --for codex
sample output 
# Continuation Pack

Project: Acme Notes
Previous agent: claude
Next agent: codex

## Goal
Implement the empty-state copy approved in the local plan.

## Files to inspect
- .contextos/tasks/active/TASK-002.md
- src/sample_app/empty_state.py

## First action
Run the focused unit test, then patch only the empty-state branch.

Illustrative sample based on v0.1.0 behavior; verify exact output with checkpoint --help.

Codex to Claude Code

Use this when a coding pass needs a debugging session in a different tool. 

checkpoint continue --from codex --for claude-code
sample output 
# Continuation Pack

Project: Sample Ledger
Previous agent: codex
Next agent: claude-code

## Current status
The parser accepts the happy path. The blank-file path still needs a clearer
message.

## Verified
- pytest tests/test_parser.py

## First action
Reproduce the blank-file path and improve the message without changing the
successful parse behavior.

Illustrative sample based on v0.1.0 behavior; verify exact output with checkpoint --help.

Resume after a break

Use this when the same person is returning after the context has gone cold. 

checkpoint continue --for cursor
sample output 
# Continuation Pack

Project: Example Calendar
Next agent: cursor

## What matters
- The current task is docs-only.
- Keep screenshots and generated assets out of the sample.
- Preserve the existing page headings.

## First action
Open the latest handoff, then update the quickstart wording.

Illustrative sample based on v0.1.0 behavior; verify exact output with checkpoint --help.