{"version":"2.1.292","anchor":"resumed-attachments-files-uploaded-without-a-sha256-trigger","canonical_anchor":"resumed-attachments-files-uploaded-without-a-sha256-trigger","heading":"Attached files without a checksum are refreshed by name when a turn is handed over","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/resumed-attachments-files-uploaded-without-a-sha256-trigger","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Attached files without a checksum are refreshed by name when a turn is handed over\n\nAfter a message with attachments, files that have no checksum can now be refreshed by name, and a new file mode treats PDFs as binary files\n\n**Unclear.** What switches the by-name refresh on, and how the `on_with_pdfs` mode is chosen, is not known.\n\n**What**\n\nWhen a message you send carries attached files and the turn is handed over to continue elsewhere, Claude Code can now refresh by name any file that was uploaded without a sha256 checksum (a fingerprint used to recognise a file). This only happens when a separate check allows it.\n\nThe setting for handling files also gains a third mode, `on_with_pdfs`, which counts PDFs as binary files. Before, the mode was only on or off.\n\n**Why**\n\nIt affects how attached files reach a turn that has been handed over, including files that could not be matched by their checksum.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}