Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
CheckpointingArea: what it touches
In DevelopmentKind: in v2.1.232,
What probably matters to youSection of the release
Rate-limit checkpoint commits plus a RESUME.md sit behind tengu_vellum_anchor, off by default, and a policy capability.
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.
Read from
Names in the bundleclaude --resume
Feature flag
tengu_vellum_anchorOff 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: off
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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up claude --resume, on Run prompts on a schedule.* Starting a fresh conversation clears all session-scoped tasks. When you resume a session with `claude --resume` or `claude --continue`, Claude Code restores the tasks scheduled with `CronCreate`, except recurring tasks that have [expired…scheduled-taskssee the edit
What has happened since
Flag reading movedThe flag server now returns off for tengu_vellum_anchor, read as this account.A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading movedThe flag server now returns nothing at all, having stopped carrying it for tengu_vellum_anchor, read as this account.A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
