{"version":"2.1.290","anchor":"pasted-images-saved-by-content-hash-into-a-tmp-dir-with-retr","canonical_anchor":"pasted-images-saved-by-content-hash-into-a-tmp-dir-with-retr","heading":"Pasted images are saved under a name based on their contents","tier":"notice","area":"File Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/pasted-images-saved-by-content-hash-into-a-tmp-dir-with-retr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Pasted images are saved under a name based on their contents\n\nPasted images are now saved in a tmp folder as pasted-., named from their contents, with retries and a check after writing\n\n**Unclear.** When Claude Code uses the note instead of showing the image is not clear.\n\n**What**\n\nWhen you paste an image, Claude Code saves a copy to disk. That copy is now different in a few ways:\n\n- It goes into a `tmp` folder inside the job's folder.\n\n- Its name is `pasted-<sha12>.<ext>`, built from a short fingerprint of the image's contents, instead of from the paste's own number. The same image pasted twice gets the same name.\n\n- Saving is retried if it fails, and the saved file is checked afterwards.\n\nThere is also a new way of handing the image on: instead of showing it, Claude Code can insert a note reading \"[Image not shown, read it from ...]\" followed by where the file was saved.\n\n**Why**\n\nThe saved file's location and name format are different, and an identical image no longer gets a fresh copy each time it is pasted.\n\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}