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.234 ·

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

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

You'll notice Improvements
JSON All of v2.1.234
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Input BoxArea: what it touches
ImprovementsKind: in v2.1.234,
ImprovementsSection of the release
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.

See this entry in the whole of v2.1.234 →

Feedback