{"version":"2.1.300","anchor":"file-sync-warning-adds-disk-full-and-name-too-long-hints","canonical_anchor":"file-sync-warning-adds-disk-full-and-name-too-long-hints","heading":"Missing-file warning now explains full disks and over-long file names","tier":"notice","area":"Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/file-sync-warning-adds-disk-full-and-name-too-long-hints","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Missing-file warning now explains full disks and over-long file names\n\nWhen synced files may not have arrived, the warning now says if a copy failed for lack of disk space or because a file name was too long\n\n**What**\n\nClaude Code can copy files into a working area for the model. When some of them may not have arrived, it shows the model a warning with the count and the list of paths. That warning now adds advice for two causes:\n\n- No space left: a copy failed with \"no space left on device\". The model is told to free up space and to ask before deleting any of your files.\n\n- Name too long: a file name is longer than the file system allows, which is usually 255 bytes.\n\nClaude Code spots these by reading the error from the failed copy, such as a write that failed with `ENOSPC` or a folder creation that failed with `ENAMETOOLONG`.\n\n**Why**\n\nThe model gets a reason it can act on, instead of only a list of files that did not arrive.\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}