{"version":"2.1.280","anchor":"user-input-pipeline-gains-explicit-inline-pastes-handling-al","canonical_anchor":"user-input-pipeline-gains-explicit-inline-pastes-handling-al","heading":"Inline pastes now flow through more of the message pipeline","tier":"internal","area":"Input Handling","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/user-input-pipeline-gains-explicit-inline-pastes-handling-al","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Inline pastes now flow through more of the message pipeline\n\nPasted text that stays inline in a message (inline_pastes) is now read, threaded through, and exposed to the Task tool and bridge messages.\n\n**Unclear.** What triggers inline_pastes versus pasted_content, and what user-visible behavior results from the chunking or truncation, are not stated in the finding.\n\n**What**\n\n- The message-ingestion step that processes attachments now reads and passes through a new `inline_pastes` field on incoming user messages, alongside the existing `pasted_content` field (used when the host extracts pasted text out of the message instead of leaving it inline).\n\n- The Task tool's input schema now accepts `inline_pastes`, a list of pasted-text entries that stay in place inside the message content.\n\n- The internal message parser and the peer\/bridge message poster now also read and forward `inline_pastes`, along with a `from_plugin` field, and messages get tagged with `plugin` when their origin is known.\n\n**Why**\n\nThis lets pasted text that intentionally stays inline (as opposed to being pulled out into a separate attachment) survive consistently across the input pipeline, the Task tool, and remote\/bridge sessions instead of being dropped or only partly supported.\n\n- Area: Input Handling\n- Names: `inline_pastes`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}