{"version":"2.1.280","anchor":"new-floor-gone-refusal-reason-for-git-checkpoint-capture","canonical_anchor":"new-floor-gone-refusal-reason-for-git-checkpoint-capture","heading":"New 'floor_gone' refusal reason for git-checkpoint capture","tier":"notice","area":"Git Checkpoints","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-floor-gone-refusal-reason-for-git-checkpoint-capture","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New 'floor_gone' refusal reason for git-checkpoint capture\n\nCheckpoint capture now refuses with a clear message when the commits it was based on are gone from history\n\n**Unclear.** The finding does not say what the exact user-facing message text is or what happens after the refusal.\n\n**What**\n\nClaude 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.\n\n**Why**\n\nPreviously 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.\n\n- Area: Git Checkpoints\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}