{"version":"2.1.229","anchor":"clearer-message-when-a-request-is-rejected-as-too-large","canonical_anchor":"clearer-message-when-a-request-is-rejected-as-too-large","heading":"Clearer message when a request is rejected as too large","tier":"notice","area":"Error Messages","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/clearer-message-when-a-request-is-rejected-as-too-large","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Clearer message when a request is rejected as too large\n\nIf a request is too big, you're told whether dropping attachments or compacting would help.\n\n**What**\n\nOn an HTTP 413 from the API, Claude Code now measures the request body and how much of it is images and documents, then tells you whether removing attachments or compacting could make it fit or whether nothing in the request is strippable.\n\n**Details**\n\n- The size threshold used for the explanation comes from a remote config value named `tengu_wobbly_fern`, falling back to a built-in limit when no value is supplied.\n- Details of the oversized request are logged as a `request_body_over_limit` line.\n\n**Evidence**\n\n`so removing attachments or compacting cannot make it fit.`\n\n- Area: Error Messages\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}