What
- The message-ingestion step that processes attachments now reads and passes through a new
inline_pastesfield on incoming user messages, alongside the existingpasted_contentfield (used when the host extracts pasted text out of the message instead of leaving it inline). - The Task tool's input schema now accepts
inline_pastes, a list of pasted-text entries that stay in place inside the message content. - The internal message parser and the peer/bridge message poster now also read and forward
inline_pastes, along with afrom_pluginfield, and messages get tagged withpluginwhen their origin is known.
Why
This 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.
Names in the bundleinline_pastesfrom_plugin
Documented inclaude-code/agent-sdk/typescript
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up from_plugin, on Compliance API.
- `from_plugin_version_id: optional string or null`api/compliance see the edit
Confirmed since
Anthropic's documentation has since written up inline_pastes, on Agent SDK reference - TypeScript.
Set `inline_pastes` to tell Claude Code which parts of `message.content` the user pasted rather than typed, one string per paste. The prompt text stays where the user put it. Claude Code may wrap each listed paste in `<pasted_content>` tag…agent-sdk/typescript see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up inline_pastes, on Agent SDK reference - TypeScript.