If a request is too big, you're told whether dropping attachments or compacting would help.
What's wrong with this entry?
On 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.
- 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. - Details of the oversized request are logged as a
request_body_over_limitline.
so removing attachments or compacting cannot make it fit.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
Connection errors say what actually went wrong
Both mention error message
-
v2.1.227
Lock release failures now say what went wrong
Both mention error message
-
v2.1.227
Structured-output failures name model fallback as the cause
Both mention error message