Claude Code v2.1.223 ·
Attachment upload failures reported back to the model per file
Attachments that fail to upload are now reported per file instead of silently vanishing.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
AttachmentsArea: what it touches
ImprovementsKind: in v2.1.223,
ImprovementsSection of the release
What
When a bridge attachment fails to upload, the tool result now says so per file instead of silently omitting it.
Details
- The attachment schema gained an optional
upload_error string, populated on failure. - The tool result splits attachments into delivered and failed sets.
- A result with any failure is marked as an error and lists each failed path with its error string, alongside a count of attachments that were included.
Evidence
upload_error: w.string().optional()
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.223 →
