{"version":"2.1.305","anchor":"image-attachment-path-gets-a-new-flag-and-a-different-file-n","canonical_anchor":"image-attachment-path-gets-a-new-flag-and-a-different-file-n","heading":"Downloaded attachments can be saved under a different file name","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/image-attachment-path-gets-a-new-flag-and-a-different-file-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Downloaded attachments can be saved under a different file name\n\nThe step that saves fetched attachment files gained an option that names them differently, based on the file's ID\n\n**Unclear.** It is not clear when the new naming option is used.\n\n**What**\n\nWhen Claude Code fetches an attached file, such as an image, it saves it locally under a generated name. That step now has an extra option. When it is on, the name comes from a different rule applied to the file's ID. When it is off, the name is the first 8 characters of the file's ID, or a random ID for images, as before.\n\n**Why**\n\nFile names of downloaded attachments may differ from what you saw before.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}