Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

SDK permission handling drops the 'leave questions standing' mode

The leaveQuestionsStanding teardown mode for pending permission questions is gone, and host-answered prompts are now tracked when the host owns input

Group of 4 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SDKArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

Unclear The finding does not say what the recorded answers are used for.

What

The internal 'leave questions standing' mode, which rejected pending permission and question prompts with "the session is being torn down" when a session shut down, has been removed. This affects sessions driven through the SDK or stream-json, where another program hosts Claude Code and answers its prompts.

  • leaveQuestionsStanding, the leftStanding state, the questionsLeftStanding hook and the teardown rejection message are gone. questionsFrozen() no longer depends on it.
  • handleElicitation no longer returns cancel because questions were left standing; it cancels only when input is closed or the request was aborted.
  • Only the shutdown check now decides whether a control_response is left for the next process, and replies left standing are no longer counted.
  • When the host owns standard input, successful can_use_tool answers that were not forwarded are recorded in hostDialogAnsweredRequestIds. Settling a prompt clears that list.
  • When no prompt is left pending, the session state flips back from requires-action.

Why

This changes what happens to pending permission prompts when an SDK or remote session is torn down mid-question: they are no longer rejected through a separate teardown mode. Hosts that relied on the teardown message should check how their pending prompts now settle.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what the recorded answers are used for.

See this entry in the whole of v2.1.281 →

Feedback