You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Git CheckpointsArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What
Claude Code can save checkpoints of a session's work, which are captured and uploaded based on the git commits present at the time. If those original commits later get rewritten or removed from the checkout's history (for example by a rebase or history rewrite), a new capture attempt now refuses to proceed. This refusal has its own internal reason code, floor_gone, and shows a dedicated message explaining what happened.
Why
Previously this situation could presumably fail in a less clear way. Now, if you rewrite git history after Claude Code has uploaded checkpoints based on it, you'll get an understandable explanation instead of a confusing failure when the tool tries to capture further changes.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what the exact user-facing message text is or what happens after the refusal.
