Running into this?

I send a second message while the agent is working; Claude Code shows it as «queued», but it reaches the agent in the middle of the task instead of when the task is done, and the agent drops the half-done work to answer it

I talk to my agents through OptionOS's Speak with «Send When the Agent Is Done» on: what I say while the agent is working is written into the chat box but not sent, and waits in the card with ⏱; whatever I say next piles up next to it. When the agent's turn ends, Enter is pressed on its own and it all goes as one message.

beforeClaude Code's queue: the second message cut in after step 2 of a 3-step task
aftertoday 18 messages held until the agent was done · 17 went when the turn ended · 0 left behind after a turn ended
Install OptionOS, keep Speak › Send When the Agent Is Done on, press ⌥A to talk while the agent works, ⌥A to finish, then ⌥⇧V: it goes when the agent is done
Text for your agent · 36 lines
Situation: the person gave an agent a task in Claude Code, thinks of something else while the agent is working, and types and sends it. Claude Code shows the message as «queued»; the person assumes it will go when the task is done, but it reaches the agent in the middle of the task: the agent leaves the half-done work to answer the new message, then goes back to the main task or doesn't.

Why: Claude Code's queue hands the message to the agent not when the agent's turn ends but as soon as the tool calls running right now finish, inside the same turn. In my setup (Claude Code 2.1.325) I gave the agent three separate 20-second commands and sent a second message at second 30: it reached the agent after the 2nd command, the agent answered it, and only then ran the 3rd command. anthropics/claude-code#50246 tracks this as an open request. OptionOS's Agents part looks at the turn state in Claude Code's session record and presses Speak's Enter when the agent's turn ends. On 16 November 2026, 18 messages of mine waited this way: 17 went when the turn ended, and I took 1 back myself before the turn ended.
This only works in Claude Code and only for what you send by talking through OptionOS: it doesn't touch a message you type and send with Enter yourself, and Codex or a chat in the browser doesn't publish its turn state, so there Enter is pressed right away.

Do:
1. First check whether OptionOS is already installed:
   ls -d /Applications/OptionOS.app ~/Applications/OptionOS.app
   Every path printed is an installed copy; if one of the paths is missing the command prints "No such file or directory" and exits with 1, which does not mean "not installed": look at the printed line. If a copy exists, don't install and don't copy over it (copying over an old copy mixes two versions and breaks the signature); note that path as "the app's path", open it with open -a <the app's path> (if it is already running nothing changes) and go to step 6.
2. Ask the person: OptionOS is a paid Mac app. Show them the price on https://optionos.app/pricing: there is a discounted first-month offer (the end date is on the page), then $24.90 a month (excluding tax), renewing automatically until they cancel; there are also 6- and 12-month plans. Don't download without their approval.
3. Download and mount the disk image at a fixed place:
   curl -fL -o /tmp/OptionOS.dmg https://optionos.app/download
   hdiutil attach -nobrowse -readonly -mountpoint /tmp/OptionOS-dmg /tmp/OptionOS.dmg
   (On newer macOS hdiutil may print a "deprecated" warning here and in step 5, and "CRC32" lines here; these are not errors, step 4 shows whether the disk is mounted.)
4. Check the signature; if you don't see "accepted" and "source=Notarized Developer ID", don't install:
   /usr/sbin/spctl -a -vv /tmp/OptionOS-dmg/OptionOS.app
   "invalid API object reference" means there is no app at that path: run step 3 again from the start.
5. Copy it into Applications, eject the disk, delete the download, open it; the app's path is now /Applications/OptionOS.app:
   ditto /tmp/OptionOS-dmg/OptionOS.app /Applications/OptionOS.app
   hdiutil detach /tmp/OptionOS-dmg
   rm /tmp/OptionOS.dmg
   open -a /Applications/OptionOS.app
   If ditto prints "Permission denied", the account can't write to /Applications: run the ditto and open lines with ~/Applications instead of /Applications (ditto creates the folder if it is missing; if ditto prints "Cannot get the real path for source", run step 3 again from the start first); the app's path becomes ~/Applications/OptionOS.app.
   Tell the person: the setup window that opens asks for permissions one by one; without the Microphone permission speech doesn't turn into text. The person grants the permissions themselves; you can't.
6. Ask the person (you can't see the menu): in the menu bar, does OptionOS › Speak show a ✓ next to «Send When the Agent Is Done»; if not, they click the row once.
7. Show the person the first use, and do it together once:
   - Give Claude Code a task that takes more than a minute (for example «run perl -e 'select(undef,undef,undef,20)' three times as three separate Bash calls, one after another, in the foreground without sending them to the background, then write DONE») and click the chat box while the agent works.
   - Press ⌥A once, say your second request, press ⌥A again: recording stops and the text waits in the card next to the cursor.
   - Press ⌥⇧V: the text lands in the chat box but isn't sent, and ⏱ shows on the card.
   - If you like, talk once more and press ⌥⇧V: the new words pile up next to the earlier ones.
   - When the agent writes DONE, Enter is pressed on its own and what piled up goes as one message.

Verify:
- In step 7, after ⌥⇧V the text stays in the chat box until the agent writes DONE, then goes on its own. The person sees this; if you can't see the screen, ask them.

Don't: send the message into Claude Code's own queue with Enter while the agent works and assume it will go when the task is done; and don't press Enter yourself on words that should wait: OptionOS presses Enter when the agent's turn ends.