{"version":"2.1.286","anchor":"bridge-attachment-handling-prefetch-release-refused-early","canonical_anchor":"bridge-attachment-handling-prefetch-release-refused-early","heading":"Attachments sent over a remote connection are tracked and cleaned up more carefully","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/bridge-attachment-handling-prefetch-release-refused-early","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Attachments sent over a remote connection are tracked and cleaned up more carefully\n\nFiles attached through a remote connection now get a note when unverifiable, and early-downloaded copies are released when unused\n\n**Unclear.** The exact wording of the new prompt note and the purpose of the extra download header are not known.\n\n**What**\n\nThis affects files attached to messages that reach a session through a remote connection.\n\n- Missing checksum: some attachments arrive without a sha256 checksum, a fingerprint used to confirm the file is intact. Claude Code now counts these and adds a note about them to the start of the prompt.\n\n- Delivery count: Claude Code now records how many attachments were actually delivered.\n\n- Early downloads: Claude Code can download an attachment before it is needed, which is called prefetching. These early copies used to expire on a fixed timer. They can now also be dropped when they go unused, or refused early.\n\n- Requests: downloads of prefetched files send an extra header, and attachment uploads now identify Claude Code as the sender.\n\n**Why**\n\nAttachments sent from elsewhere are delivered more reliably. When one is not delivered or cannot be verified, that is now easier to see.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}