What
If you type a prompt while Claude is still working, it is queued to run after the current turn. When Claude Code is connected to your code editor (IDE), the text you have selected there is your IDE selection. That selection now stays attached to the queued prompt:
- When a prompt is queued, the current IDE selection is taken and stored with it as
ideSelection. This does not happen in bash mode. - Queued prompts that carry a selection show it, shortened, in a row under the prompt.
- When the queued prompt runs, its own stored selection is used rather than whatever is selected at that moment.
- The selection and any opened-file details stored with each queued prompt are sent along with it.
- If a UserPromptSubmit hook drops the queued prompt, the prompt and its selection are handed back to the input box, as long as no other queued prompt is holding a selection. A hook is a script you configure to run at set points; this one runs when a prompt is submitted. The "Prompt dropped by a hook" notice still shows.
- When queued prompts are pulled back into the input box for editing, their selections come back too. Stepping back through queued prompts stops at one that has a selection.
The queue hint now shows only while the prompt input is on screen. Two reminders, silent_turn_reminder and total_tokens_reminder, are skipped in one case: when the queued prompt was already delivered at the start of the turn.
Why
The code you had selected when you typed a queued prompt now goes with that prompt. Before, it could be lost or picked up by whatever ran next.