{"version":"2.1.315","anchor":"auto-mode-new-notice-when-desktop-turned-the-safety-check-o","canonical_anchor":"auto-mode-new-notice-when-desktop-turned-the-safety-check-o","heading":"Auto mode now tells you when it falls back to its own billed safety check","tier":"notice","area":"Auto Mode","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/auto-mode-new-notice-when-desktop-turned-the-safety-check-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Auto mode now tells you when it falls back to its own billed safety check\n\nWith a gateway set, auto mode now shows a notice when gateway checks are not working and it is using its built-in check, which sends extra billed requests\n\n**What**\n\nAuto mode is a way of running Claude Code where a safety check decides whether Claude's actions can go ahead without asking you. Some setups send that check through a gateway, which is a server your organization runs between Claude Code and the model.\n\nWhen a gateway is configured and the desktop app has turned the safety check on, auto mode now shows a notice. The notice says the gateway's checks are not working in this session, so Claude Code has switched to its own built-in check for the rest of the session. The built-in check sends extra requests, and those requests are billed.\n\n**Why**\n\nIf you rely on a gateway, this notice tells you that your checks are no longer going through it and that you may be charged for the extra requests.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}