Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Rate-limit checkpoint can commit in-progress work to a hidden git ref

Not switched on
Useful4 Signal5
Checkpointing Notable

Before a usage limit cuts you off, your work can be committed to a hidden git ref with resume notes.

Rate-limit checkpoint commits plus a RESUME.md sit behind tengu_vellum_anchor, off by default, and a policy capability.

Feature flag
tengu_vellum_anchor Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.232: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.232. It isn't a statement about your account. What a flag value here can and cannot tell you

claude --resume
What

New machinery commits your working tree, tracked and untracked files, to a Claude-owned git ref before a usage limit ends the session, plus a RESUME.md note listing the current TodoWrite plan and the claude --resume <id> command to pick it back up. The near-limit call site is behind the remote-config flag tengu_vellum_anchor, whose built-in fallback is off, and the commit additionally requires a policy capability.

Details
  • The commit is authored with user.name=Claude Code and stored under a dedicated ref namespace, so it does not appear in your branches or history.
  • The resume file is appended to .git/info/exclude; checkpoint refs older than two weeks are pruned.
  • It refuses in many situations, recording skip reasons including non_interactive, remote_workspace, bare_repo, sparse_checkout, content_filters, sequencer_in_progress, gitdir_uncontained and too_large.
Evidence

refs/claude/checkpoint-

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.

See this entry in the whole of v2.1.232 →