Pinning Checkpoints
Protect the state you care about most from automatic cleanup.
Premium featurePin protects a snapshot from the manual Clear Snapshots command. When you clear, the pinned snapshot and everything before it in the incremental chain is kept. It is the one cleanup operation where you have explicit control over what survives.
A pin does not survive a git commit or branch switch. Those events wipe all snapshots including the pinned one. This is intentional — a snapshot from branch A has no meaning on branch B and should not persist there.
How to pin
Right-click any snapshot in the sidebar → Pin Snapshot. A pin icon appears on the snapshot. Moving the pin is instant — just pin a different snapshot and the previous pin is released automatically.
Single-pin model
StateSense enforces a single-pin model intentionally. Only one snapshot can be pinned at a time. If you pin a new snapshot, the previous pin is released automatically.
This design matches how StateSense's retention engine actually works: the pinned snapshot defines the earliest state you can reliably restore to. Having multiple pinned snapshots would give a false sense of protection.
What pin protection means
When a snapshot is pinned, StateSense preserves that snapshot and all snapshots before it in the incremental chain. This is necessary because restoring the pinned snapshot requires replaying all earlier snapshots to reconstruct the state.
Snapshots after the pinned one are removed when you run Clear Snapshots.