{"version":"2.1.273","anchor":"new-prompt-attachment-extraction-step-inserted-into-user-mes","canonical_anchor":"new-prompt-attachment-extraction-step-inserted-into-user-mes","heading":"New prompt-attachment extraction step inserted into user message pipeline","tier":"internal","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-prompt-attachment-extraction-step-inserted-into-user-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New prompt-attachment extraction step inserted into user message pipeline\n\nA new step can extract prompt attachments and insert them as extra messages right after the first message\n\n**Unclear.** What triggers `extractPromptAttachments` to be set, and what kind of attachments this applies to, isn't stated.\n\n**What**\n\nWhen a new flag, `extractPromptAttachments`, is set on parsed input, Claude Code now runs an additional processing step that builds extra messages from the input and inserts them into the message list immediately after the first message.\n\n**Why**\n\nThis adds a way for attachments carried in a prompt to be pulled out and turned into their own messages, when this flag is enabled.\n\n- Area: Agents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}