{"version":"2.1.323","anchor":"image-attachments-get-a-name-when-inlined-tengu-plain-locke","canonical_anchor":"image-attachments-get-a-name-when-inlined-tengu-plain-locke","heading":"Images attached through a connected app now keep their file names","tier":"notice","area":"File Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/image-attachments-get-a-name-when-inlined-tengu-plain-locke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Images attached through a connected app now keep their file names\n\nWhen an image attachment is placed directly in the conversation, Claude now gets its file name as well as its path\n\n**What**\n\nWhen an attachment arrives from a connected app and turns out to be an image, Claude Code can place it directly in the conversation. Before, Claude got only the file paths of such images. Now the image record also carries each file's name.\n\nThis is controlled by a remote switch that is on when the server sends nothing.\n\n**Why**\n\nClaude can see the real names of images you upload rather than only paths that mean nothing to it.\n\n- Flag `tengu_plain_locket`: Not enough to say (read for one account on one subscription tier against v2.1.323; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}