{"version":"2.1.293","anchor":"oversized-mcp-uploadanswer-400-with-a-specific-reason-maps","canonical_anchor":"oversized-mcp-uploadanswer-400-with-a-specific-reason-maps","heading":"Uploads rejected as too large are now reported as their own kind of failure","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/oversized-mcp-uploadanswer-400-with-a-specific-reason-maps","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Uploads rejected as too large are now reported as their own kind of failure\n\nWhen the server rejects an upload as too large, Claude Code now records it as a too-large failure instead of a general one\n\n**Unclear.** It is not clear which uploads this covers or what you see when one is too large.\n\n**What**\n\nWhen an upload is refused by the server with a particular \"bad request\" reason, Claude Code now records the failure as too large. That flag is passed on in the reply it sends back. The message for an unauthorised upload is unchanged in meaning.\n\n**Why**\n\nAn upload that is too big can now be told apart from other failed uploads.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}