If you have too many untracked files, cloud seeding refuses and tells you which budget you blew.
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.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.
Read once, for one account on one subscription tier, against v2.1.224. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
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.
- Same gating as the seeding feature itself: the
tengu_violin_woodgate plusremoteFileModeset tocontainer_sync. - The fallback is bundle-only seeding, and the existing seed telemetry records a
too_many_untrackedoutcome.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Folder-seed refusals name the size, the cap and the largest files
Both mention gitignore