{"version":"2.1.283","anchor":"chrome-file-upload-refuses-hard-linked-files-with-a-clear-re","canonical_anchor":"chrome-file-upload-refuses-hard-linked-files-with-a-clear-re","heading":"Chrome file uploads say why a file was refused, including hard-linked files","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/chrome-file-upload-refuses-hard-linked-files-with-a-clear-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Chrome file uploads say why a file was refused, including hard-linked files\n\nChrome file uploads now give a specific reason for a refusal, and hard-linked files get an explanation and a suggested fix\n\n**Unclear.** How the earlier error messages for these cases read is not known.\n\n**What**\n\nWhen Claude Code uploads a file through its Chrome browser integration, a refused upload now names one specific reason:\n\n- the path is not a regular file\n\n- the file has more than one hard link\n\n- the file was moved\n\n- the file is too large\n\n- the file grew during the upload\n\nA hard link is a second name pointing to the same file on disk. The hard-link message explains that such a file can stand in for a file outside the folders the session is allowed to use. It adds that this often happens inside `node_modules`, because Bun and pnpm hard-link packages, and suggests copying the file (for example with `cp`) and uploading the copy.\n\n**Why**\n\nAn upload failure that used to be confusing now says what went wrong and how to get around it.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}