You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
New FeaturesKind: in v2.1.224,
New FeaturesSection of the release
What
When the untracked files at your git root exceed the seeding budget, the upload is refused and you are told why instead of quietly starting from the git bundle alone. There are two messages: one counting files against the 192-file budget, one counting bytes against the 100 MB transfer budget, and the byte one suggests adding a .gitignore entry.
The fallback is bundle-only seeding, and the existing seed telemetry records a too_many_untracked outcome.
Evidence
untracked files exceed the v0 seed budget of, of untracked files exceed the v0 seed transfer budget of
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Names in the bundle.gitignore
Feature flag
tengu_violin_woodOff 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.224: not a boolean we can read
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.
Flag reading movedThe flag server now returns off for tengu_violin_wood, 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_violin_wood, 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.
