{"version":"2.1.233","anchor":"proxy-guidance-now-says-to-relay-anthropic-s-400-and-413-mes","canonical_anchor":"proxy-guidance-now-says-to-relay-anthropic-s-400-and-413-mes","heading":"Proxy guidance now says to relay Anthropic's 400 and 413 messages","tier":"notice","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/proxy-guidance-now-says-to-relay-anthropic-s-400-and-413-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Proxy guidance now says to relay Anthropic's 400 and 413 messages\n\nProxy guidance now says to pass through 400 and 413 error text so auto-compact can react.\n\n**What**\n\nThe proxy-writing guidance bundled with the gateway docs still tells you to log upstream errors and return a generic message preserving `error.type`, but now makes an exception: if a 400 or 413 arrives in Anthropic's own error envelope, relay its `error.message`, because client-side recovery such as auto-compact keys on that text.\n\n**Details**\n\n- The guidance text appears twice in the gateway docs and both copies changed.\n\n**Evidence**\n\n`own error envelope (e.g. \\`prompt is too long: \\u2026\\`): relay that`\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}