Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Editing a queued command keeps its mode and refuses on a dirty draft

You'll notice
Useful3 Signal1
Input Box

Editing a queued entry keeps its mode, and a queued shell command only comes back if the input is empty.

What

Pulling a queued entry back into the input box now restores the entry's own mode instead of always switching to prompt mode. A queued shell command can only be pulled back when the input is empty; otherwise you get a two-second notice saying "Clear the input to edit this queued shell command" and nothing is pulled.

Details
  • The refusal is recorded as bash_needs_empty_draft; a pull that targets an entry that is no longer there is recorded as stale_index. Both go to the input_queue_pop_to_edit counter.
  • Pulling an entry also clears the stored queue-edit position.
  • A separate new path lets a queued message be sent right away by interrupting the running turn, recorded as input_send_queued_now with no_live_controller as its failure reason. That path needs an enablement check, prompt mode and an active query.
Evidence

Clear the input to edit this queued shell command

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.234 →