{"version":"2.1.128","anchor":"better-large-input-and-media-result-messages","canonical_anchor":"better-large-input-and-media-result-messages","heading":"Better Large Input and Media Result Messages","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.128\/e\/better-large-input-and-media-result-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.128","markdown":"### Better Large Input and Media Result Messages\n\nClaude Code now explains size and media limits more directly.\n\n**Details**\n\n- Piped stdin that exceeds the size cap tells users to pass large content as a file path.\n- Oversized remote requests tell users to shorten the prompt or send it in parts.\n- Media rejected by the API is replaced with an explicit placeholder instead of failing opaquely.\n- PDF content returned by inner `Read` calls can be surfaced as document content blocks.\n\n**Evidence**\n\nUser-facing limit messages (search for `\"piped stdin input exceeds\"`, `\"request exceeds\"`, `\"(media removed \u2014 rejected by API)\"`, and `\"PDFs returned by inner Read calls\"`)"}