{"version":"2.1.300","anchor":"staged-file-placement-telemetry-now-splits-no-space-and-name","canonical_anchor":"staged-file-placement-telemetry-now-splits-no-space-and-name","heading":"Staged-file warnings now say why files were not placed","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/staged-file-placement-telemetry-now-splits-no-space-and-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Staged-file warnings now say why files were not placed\n\nWhen staged files fail to land, the warning now counts how many failed for lack of space and how many because the name was too long\n\n**What**\n\nStaged files are files copied into a cloud session ahead of time. When some of them fail to land where they should, Claude Code logs a warning and records a count. Two new counts are now included:\n\n- `no_space`: files that could not be placed because there was no room\n\n- `name_too_long`: files that could not be placed because their name was too long\n\nThe separate note telling the model that files may be missing still depends on a server-side switch. That switch is off unless it is turned on remotely. The flag server has returned off for this site's account and for an anonymous check.\n\n**Why**\n\nThe warning now shows the reason files went missing in cloud sessions, not just how many. A full disk and a too-long file name can be told apart.\n\n- Flag `tengu_ochre_dunlin`: Off in both readings (read for one account on one subscription tier against v2.1.300; this account: off, anonymous baseline: off, compiled default: 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.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}