{"version":"2.1.280","anchor":"new-auto-mode-check-unavailable-ui-state-for-the-auto-mode","canonical_anchor":"new-auto-mode-check-unavailable-ui-state-for-the-auto-mode","heading":"Auto mode now backs off and stops the turn if the server-side safety check stays unavailable","tier":"notice","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-auto-mode-check-unavailable-ui-state-for-the-auto-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Auto mode now backs off and stops the turn if the server-side safety check stays unavailable\n\nAuto mode now shows a countdown and eventually stops the turn if its server-side safety check keeps failing\n\n**What**\n\n- When Auto mode's server-side safety classifier repeatedly returns no usable verdict, Claude Code now waits with backoff and reports this as a new `auto_mode_unavailable` retry status.\n\n- The UI shows a matching new state, 'Auto mode check unavailable', with a countdown ('next try in \u2026 attempt X\/Y') and a hint that you can press escape to interrupt.\n\n- After a fixed number of consecutive failures, Claude Code stops retrying, denies the tool call, and ends the turn instead of looping forever. This is tracked by the `tengu_auto_mode_unavailable_stop` event.\n\n**Why**\n\nWithout this, a server-side classifier outage could leave Auto mode retrying indefinitely with no clear feedback. Now you see what's happening and the turn eventually gives up cleanly instead of hanging.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}