Multi-Hour Task Checkpointer
$1.99OfficialInvoke when an autonomous task may outlast one context window—persist resumable checkpoints to a state file so work survives resets and interruptions.
What you get
- ✓9-step procedure
- ✓Runnable Python / JSON included
- ✓8-point quality checklist
- ✓8 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 7 min read
- Requires
- Works with any modern AI assistant
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Invoke at the start of any autonomous task expected to exceed one context window or ~30 minutes of wall-clock work: large refactors, multi-repo migrations, batch data processing, long test-and-fix loops, corpus generation, crawl/ingest jobs. Also invoke mid-task the moment context usage climbs past ~65% with work remaining, or immediately before any operation that may truncate history (spawning a fresh session, compaction, a tool that returns a huge payload). Do NOT use for tasks that finish in a handful of tool calls — the bookkeeping overhead is not worth it. The dividing line: if losing all in-memory state right now would cost more than ~5 minutes to reconstruct, c
…
🔒 Buy once ($1.99) to unlock the full playbook, download it, and install it in every tool you use.