Claude Code: Anatomy of a Misfeature

git log -1 --format='%h %ai' -S'## 2.1.198' -- CHANGELOG.md # 75709eac 2026-07-01 20:45:29 +0000 #The misfeatureAskUserQuestion is the tool Claude Code uses to stop and ask the human a question mid-taskNew behaviour: after 60 seconds of inactivity, the tool auto-returns a “proceed anyway” result instead of blockingThe message handed back to the model — this is the template, rendered here at the 60-second default:// v2.1.198, verbatim. `Thl` is the minifier's name; the prose is the binary's own. // Note "60s" is interpolated, not a literal in the file: function Thl(e){return `No response after ${Math.round(e/1000)}s — the user may be away from keyboard. Proceed using your best judgment based on the context so far; you can re-ask this question later if it's still relevant.`} The “re-ask later” escape hatch is circular: the re-asked question hits the same timeout. Aleksey Nogin made this point in the issue thread within minutes of filing itThe transcript line has two variants — the binary picks between them on whether you’d started answering:// v2.1.198, verbatim. `a` is the minifier's name for "some answers exist" // (`s=Object.entries(r)` over the answers, `a=s.length>0`); both string values // are the binary's own. let d=a?"continued with the answers selected so far":"continued without an answer" So a half-answered dialog does not discard the partial input — it submits it. Answer question one of three, step away, and the timeout commits your one answer plus whatever the model picks for the other twoBoth strings are absent from 2.1.197 and present in 2.1.198In fairness: it was not silent on screen. The dialog rendered a live countdown, and a keypress restarted the timer.

Assembled at runtime rather than stored as one string, so this is the rendered form, not a literal grep hit:// v2.1.198, verbatim — the pieces. `s` is the remaining-seconds value. children:["auto-continue in ",s,"s \xB7 any key to stay"] // renders as: auto-continue in 12s · any key to stay Which cuts less far than it looks. The countdown only reaches someone watching the screen, and the premise of the feature is that you aren’t:the internal name is AFK; the message says “the user may be away from keyboard”running several agents at once, “watching the screen” is not one place — the countdown you needed was on another tabAnd the countdown is late. The threshold defaults to 20 seconds (CLAUDE_AFK_COUNTDOWN_MS), and it gates on remaining time, not elapsed — so for the first 40 seconds the dialog looks like an ordinary blocking question. It is on screen, but nothing on it says a timer is running:// v2.1.198 ships this minified — the locals are mangled, but the property // names survive, so `showCountdown` and `remainingSeconds` are its own words: let u=i*1000<=n;return{remainingSeconds:i,showCountdown:u,timeoutMs:t} // ...which reads, with n at its default of 20000: showCountdown = remainingSeconds * 1000 <= 20000 The warning arrives in the last thirdWhat it does not touch: the timeout applies only to AskUserQuestion. Anthropic’s tools reference says “permission prompts, including plan approval, never auto-resolve on idle” — and unlike the docs claims elsewhere in this post, this one is checkable against the shipped 2.1.198 code rather than a page written after the fix:the countdown component (q0m) has exactly one call site in the entire bundle, and its timer hook (_Rc) has exactly one caller — q0m itself.

The timer exists in one componentthat component’s props identify it past argument: jsx(dRc,{question:V, questions:s, currentQuestionIndex:$, answers:R, questionStates:O, onAnswer:be, onSubmit:N, …}). Its timeout handler is what fires tengu_ask_user_question_afk_auto_advancethe permission prompt (Do you want to proceed, Do you want to allow …) is a separate component with no timer attachedBut the exemption only protects you if a permission prompt appears at all. 2.1.198 ships bypassPermissions, acceptEdits, allowedTools, --dangerously-skip-permissions and PreToolUse hooks. Anyone running agents against deployments has plausibly allowlisted the deploy command or turned prompts off — that is what automating it means. For them the permission layer was never going to fire, so its immunity to the timer buys nothingThe narrower claim, and the one that bites: the timer could not grant permission, but it could make the choice. AskUserQuestion doesn’t ask permission, it asks you to decide — “staging or production?”, “which config?” On timeout the model is told to proceed using your best judgment, and the partial-answers path continues “with the answers selected so far”. If permission was already granted by allowlist or bypass, the choice was the only gate leftNo timeout parameter exists in the tool schema — the model can neither set nor control it. Verified in the binary (U_f=…H.strictObject({questions:…})), not taken from the issue thread. The input params are only:questions, answers, annotations, metadata So the model is truthful when it says it didn’t skip anything — the harness returned the answer, not the model#The fix2.1.200 made auto-continue off by defaultIdle timeout is now opt-in via /config, not forced on everyoneNote the changelog’s verb: “no longer auto-continue by default”. Nothing was removed — the default flipped.The /config setting the note points you to did not exist before the fix. Grep 2.1.198 for askUserQuestionTimeout and you get zero hits: when this shipped, the only way to escape it was an env var — and the release notes never named it.