{"version":"2.1.281","anchor":"auto-mode-server-fallback-notice-records-why-it-went-unanswe","canonical_anchor":"auto-mode-server-fallback-notice-records-why-it-went-unanswe","heading":"Auto-mode server-fallback notice records why it went unanswered","tier":"internal","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/auto-mode-server-fallback-notice-records-why-it-went-unanswe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Auto-mode server-fallback notice records why it went unanswered\n\nThe auto-mode server-fallback notice now records \"unanswered\" when it closes without a choice, and the dialog can be cancelled from outside\n\n**Unclear.** The finding does not describe what the server-fallback notice itself tells the user.\n\n**What**\n\nWhen the auto-mode server-fallback notice is closed because the choice was cancelled, the usage report Claude Code sends, `tengu_auto_mode_server_fallback_notice_closed`, now marks it as `unanswered`. The dialog also accepts an abort signal, which is a way for other code to close it without the user answering.\n\n**Why**\n\nA notice that went away without an answer is now reported as unanswered instead of looking like a normal close.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}