{"version":"2.1.314","anchor":"upload-by-reference-error-message-depends-on-blocked-reads","canonical_anchor":"upload-by-reference-error-message-depends-on-blocked-reads","heading":"Upload error no longer suggests base64 when file reads are blocked","tier":"notice","area":"Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/upload-by-reference-error-message-depends-on-blocked-reads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Upload error no longer suggests base64 when file reads are blocked\n\nWhen a file cannot be uploaded and reading files is blocked, the error no longer suggests sending the file's base64 instead\n\n**What**\n\nWhen Claude Code cannot upload a file, it shows a message starting \"Nothing was uploaded:\". Before, this message always said the tool would still accept the file as base64, a way of writing a file's contents out as text.\n\nThe message now depends on whether reading files is blocked. When it is blocked, the base64 suggestion is left out.\n\n**Why**\n\nIf reading files is blocked, the base64 route does not work either, so the old message pointed to a fix that would fail. The new message is less misleading.\n\n- Area: Attachments\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}