{"version":"2.1.317","anchor":"auto-mode-classifier-heals-400s-by-dropping-the-beta-header","canonical_anchor":"auto-mode-classifier-heals-400s-by-dropping-the-beta-header","heading":"Auto mode keeps working through gateways that reject a safety header","tier":"notice","area":"Auto Mode","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/auto-mode-classifier-heals-400s-by-dropping-the-beta-header","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Auto mode keeps working through gateways that reject a safety header\n\nIf a request only succeeds without auto mode's safety header, Claude Code stops sending it and turns off the server-side action check\n\n**What**\n\nIn auto mode, Claude acts without asking you first. A request may be refused with HTTP error 400 or 422, or in some cases 403, and then succeed when sent again without auto mode's dangerous-tool-use beta header and safeguards field. When that happens, Claude Code stops sending them. A warning is logged.\n\nThe server-side check of Claude's actions then stays off:\n\n- for the rest of the conversation, normally\n\n- until Claude Code restarts, when you connect through a gateway\n\n**Why**\n\nIf your organization routes traffic through a gateway that rejects this header, auto mode keeps working instead of failing. Be aware that the server-side safety check of Claude's actions is off once this happens.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}