{"version":"2.1.224","anchor":"cloud-seeding-tells-you-when-there-are-too-many-untracked-fi","canonical_anchor":"cloud-seeding-tells-you-when-there-are-too-many-untracked-fi","heading":"Cloud seeding tells you when there are too many untracked files","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cloud-seeding-tells-you-when-there-are-too-many-untracked-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cloud seeding tells you when there are too many untracked files\n\nIf you have too many untracked files, cloud seeding refuses and tells you which budget you blew.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Same gating as the seeding feature itself: the `tengu_violin_wood` gate plus `remoteFileMode` set to `container_sync`.\n- The fallback is bundle-only seeding, and the existing seed telemetry records a `too_many_untracked` outcome.\n\n**Evidence**\n\n`untracked files exceed the v0 seed budget of`, `of untracked files exceed the v0 seed transfer budget of`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.224; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Cloud Sessions\n- Names: `.gitignore`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}