The usage-limit checkpoint file now explains how to roll the work back with /rewind.
What's wrong with this entry?
The "Claude Code — resume checkpoint" file written when you approach or hit a usage limit now ends with a section explaining how to roll the work back with /rewind.
- Notes that changes made by bash commands are not covered by the rewind.
- Says the saved snapshot is complete and is kept until the next checkpoint or roughly two weeks.
Don't want these changes? Resume this session (above), then run
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Snapshots report when there are too many changed paths to list
Both mention checkpoint
-
v2.1.248
Snapshot failures distinguish momentary races from real problems
Both mention checkpoint
-
v2.1.248
Work-in-progress stash snapshots restage files that moved mid-copy
Both mention checkpoint