Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Usage-limit checkpoints clean up old git references in one sandboxed step

Old usage-limit checkpoints are now removed from git in one batch, inside the sandbox when it is on, and a failure is retried next time

Under the hood Internal Changes
JSON All of v2.1.315
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
CheckpointsArea: what it touches
Internal ChangesKind: in v2.1.315,
Internal ChangesSection of the release
What

For its usage-limit feature, Claude Code saves checkpoints in git as references, which are named pointers to saved states. It also removes old ones. Several things changed:

  • Old checkpoint references are now removed together in one batch rather than one at a time.
  • When sandboxing is on (a sandbox limits what commands can read and change), that removal runs inside the sandbox.
  • If removal fails, the log says stopped deleting old checkpoint refs; the next checkpoint retries, and the next checkpoint tries again.
  • The path used for resuming is added to the repository's local exclude list, which tells git to ignore it without changing shared files.
  • Text that the server supplies for the usage-limit release and resume prompts is now checked before use, and Claude Code reports when it rejects or changes that text.
Why

The checkpoint feature now respects the sandbox when it changes your git repository, and keeps its own files out of what git tracks. Messages sent from the server for this feature are checked rather than used as they arrive.

See this entry in the whole of v2.1.315 →

Feedback