The reasoning layer for every code change
Capture the why, not just the diff.
ckpt records constraints, dead ends, and reasoning as you work — so the next person (or AI) picks up exactly where you left off. No more re-discovering what was already tried.
Context evaporates between sessions.
Every coding session produces invisible knowledge — why Redis was rejected, which approach hit a wall, what constraint the PM mentioned in passing. ckpt captures it all in a structured, portable format that travels with the code.
Constraints
“No Redis”, “must be SOC2 compliant” — the verbal rules that never make it into code comments. ckpt logs them as first-class objects.
Dead ends
Approaches tried and abandoned — with reasons. Stop the next developer from walking the same dead-end path.
Reasoning
The decision trace behind each code change. Not just what changed, but why it changed — and what alternatives were considered.
$ ckpt commit Capturing checkpoint... ✓ 3 constraints recorded ✓ 1 dead end logged ✓ 8 reasoning steps saved $ ckpt push ✓ Pushed to ckpt cloud — share link copied $ ckpt handoff --to james ✓ Handoff brief generated → James will see: constraints, dead ends, open items