{"version":"2.1.323","anchor":"bridge-attachment-upload-received-file-check-returns-causes","canonical_anchor":"bridge-attachment-upload-received-file-check-returns-causes","heading":"File uploads from remote sessions now say why a file was not counted as received","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bridge-attachment-upload-received-file-check-returns-causes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### File uploads from remote sessions now say why a file was not counted as received\n\nRemote-session file uploads now give a reason when a file is not accepted, skip symbolic links, and no longer send thumbnails\n\n**What**\n\nSome Claude Code sessions are bridged, meaning connected so that you can use them from somewhere else, such as claude.ai. In these sessions Claude Code checks whether a file counts as received before it uploads it as an attachment. That check used to give only a yes or a no. It now also gives a reason when the answer is no. The reasons include:\n\n- `too_large`: the file is too big\n\n- `outside_outputs`: the file is not in the outputs area\n\n- `entries_limit`: too many files\n\n- `hashes_limit`: too many file fingerprints to check\n\n- `no_match_link_skipped`: the file was a link and was skipped\n\nThe check now skips symbolic links (shortcut files that point to another file) and no longer follows them. Uploads can also be refused through a new refusal step. Uploads no longer include a small preview image (a thumbnail). The reason a file was turned down is now recorded in Claude Code's usage reporting.\n\n**Why**\n\nIt changes which files are uploaded from bridged and remote sessions, and it makes it easier to see why a file was left out.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}