{"version":"2.1.224","anchor":"askuserquestion-dialog-fallback-cannot-fire-in-this-build","canonical_anchor":"askuserquestion-dialog-fallback-cannot-fire-in-this-build","heading":"AskUserQuestion dialog fallback cannot fire in this build","tier":"soon","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/askuserquestion-dialog-fallback-cannot-fire-in-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### AskUserQuestion dialog fallback cannot fire in this build\n\nA fallback to the question dialog when auto-classification is unavailable can never fire here.\n\n**What**\n\nNew code lets a question fall back to the interactive dialog when the auto-mode classifier is unavailable or the conversation is too long for it, instead of failing. The condition negates a helper that always returns true here, so the branch is unreachable as shipped.\n\n**Details**\n\n- the separate classifier switch remains, readable from `CLAUDE_CODE_AUTO_MODE_CLASSIFY_ASK_USER_QUESTION` or the `classifyAskUserQuestion` field of the auto mode config\n\n**Evidence**\n\n`Auto mode classifier transcript too long for AskUserQuestion, falling back to the question dialog`\n\n- Area: Auto Mode\n- Names: `CLAUDE_CODE_AUTO_MODE_CLASSIFY_ASK_USER_QUESTION`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}