{"version":"2.1.234","anchor":"editing-a-queued-command-keeps-its-mode-and-refuses-on-a-dir","canonical_anchor":"editing-a-queued-command-keeps-its-mode-and-refuses-on-a-dir","heading":"Editing a queued command keeps its mode and refuses on a dirty draft","tier":"notice","area":"Input Box","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/editing-a-queued-command-keeps-its-mode-and-refuses-on-a-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Editing a queued command keeps its mode and refuses on a dirty draft\n\nEditing a queued entry keeps its mode, and a queued shell command only comes back if the input is empty.\n\n**What**\n\nPulling 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.\n\n**Details**\n\n- 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.\n- Pulling an entry also clears the stored queue-edit position.\n- 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.\n\n**Evidence**\n\n`Clear the input to edit this queued shell command`\n\n- Area: Input Box\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}