Before uploading your repository to a cloud session, Claude Code now checks whether the clone has truncated history and picks a workable path: bundle a narrower slice, fall back to a snapshot of the working tree with no history, or refuse with an explanation.
- The outright refusal happens when the current branch has no commits yet and the other branches are cut short; the message suggests committing first or running
git fetch --unshallow. - Cancelling the upload is now reported as aborted rather than as a failure.
- A new metric records the scope, size and build time of each bundle.
- The shallow-history probe runs only when
tengu_violin_woodis on, which falls back to off; the rest applies always.
The current branch has no commits yet, and the other branches of this shallow clone are cut short, so nothing here can be bundled; commit first, or deepen the clone (git fetch --unshallow)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_violin_wood Off in both readingsThe 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.239: off
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.