Queue a message ("send after the agent finishes")
How to line up follow-up messages that send themselves the moment the agent finishes its current step. Covers where the option lives in the composer, how the queued list is opened and managed, and the limits worth knowing before you rely on it — the 24-hour wait, the refusal on an ended session, and how several messages go over together in one turn.
On this page
What it is
While the agent is mid-step, you can queue a follow-up message that waits and sends itself the moment the current step finishes — instead of interrupting the work in progress. You can line up several messages: they deliver in order, the moment the agent is free — and when several are waiting they go over together, in one turn. This is the smooth way to capture a follow-up thought, or line up a series of related instructions, without cutting off what the agent is doing.
It's distinct from the two things it sits next to:
- Normal send (Enter) delivers immediately and, if the agent is running, interrupts the current step — see send-a-message.md. Queueing is the "don't interrupt, send it when it's done" alternative.
- Send Later (send-later.md) schedules ONE reply for a clock time. The queue holds MANY messages triggered by the agent finishing a turn, not by the clock.
Where to find it
Everything happens in the session's composer, at the bottom of the conversation. Press and hold the Send button, or click its ▾ caret, to open the Send Later picker; the same picker opens from Ctrl+Shift+L, or from the session ⋯ menu's "Send Later". The composer's ▾ caret / hold is available while the agent is running, not only when idle — so you can line this up mid-task, right where you're typing. "After the agent finishes" is the first option in that picker, above the time presets — shown only while the agent is working (running, starting up, or parked waiting for account capacity), because on an idle session there is nothing to wait for.
The queue itself is the "N messages queued" line at the bottom of the conversation; click it to open the ordered list, where each row carries its own Edit (pencil), Reorder (up / down arrows) and Remove (✕) controls.
The line sits at the transcript's foot, just below the point a running session keeps you at while it streams, so on a busy turn it can fall just past the bottom edge — scroll down a little, or tap the down arrow, to bring it into view.
How it behaves
How to use it
- Type your message in the composer as usual, while the agent is working.
- Open the send options — press and hold the Send button, or click its ▾ caret (or Ctrl+Shift+L, or the session ⋯ menu's "Send Later") to open the Send Later picker. The composer's ▾ caret / hold is available while the agent is running, not only when idle — so you can line this up mid-task, right where you're typing.
- Pick "After the agent finishes" — it's the first option in the picker (above the time presets), so pressing Enter right away picks it. Your message joins the session's queue and the composer clears. (Just queued it by mistake? The Undo toast / Ctrl+Z removes it and restores your draft.) Start typing a time instead ("2h", "tomorrow 9am") and the option steps aside, so Enter schedules that time.
- See the queue — a single "N messages queued" line appears at the bottom of the conversation. That count is your confirmation the message was queued, and it updates every time you add one. It sits in the chat itself and scrolls with it, so it is never parked over your screen (it used to be pinned above the typing box). When the queue is waiting, a short grey note beside the count says why and until when — "sends when the agent finishes its current turn", "held until this session resumes" (paused, stopped, or waiting on a usage limit), or "waits for its next turn — next wake-up at 12:45 AM" (a session resting between wake-ups, or one holding only board-post notices or in Do Not Disturb "hold everything"). Hover the note for the longer reason. No note means the queue is going out now. (Added 2026-10-11, after a resting session showed "1 message queued" and nothing else.)
- Click that line to open the list — the messages show in the order they'll send. It starts closed so the queue never covers the conversation; once you open it, it stays open for that session until you close it again.
- Manage the queue before it sends — on each row:
- Edit (pencil) — change the text inline (Enter to save, Esc to cancel).
- Reorder (up / down arrows) — move a message earlier or later; the disabled arrows mark the ends. Keyboard- and screen-reader-friendly.
- Remove (✕) — drop a message (a quick confirm, since it won't be sent).
- They send themselves. As the agent finishes each step and goes idle, the next queued message is delivered automatically — appearing as a normal message from you, kicking off the next turn. The queue drains top to bottom until it's empty.
Agent already idle? Then there's nothing to wait for, so the picker doesn't offer "After the agent finishes" at all — only the time presets — and Send Later never sends right away, even on a brand-new session that hasn't started yet. (A message queued another way — over the CLI, or by another agent — while the session is idle is delivered at once, the same as a normal send.)
Agent parked on a wait? When an agent finishes its turn and is only waiting — on a background task, a scheduled wake-up, or anything else it said it was waiting for — the session still reads as running, but a message queued for it is delivered right away rather than when the wait ends. Only a message arriving while the agent is genuinely mid-step waits for that step to finish.
When the agent finishes by asking you a question, the next queued message is still sent (it becomes your answer). If you'd rather answer a specific question yourself, remove or reorder the queued messages first — they're right there at the bottom of the conversation.
How it works
- Each session has its own queue (up to 200 messages), stored durably — it survives an app restart and picks up delivering where it left off.
- A message that has gone out, or that you removed, is kept for 7 days and then deleted. Once a queued message has been delivered or removed, the app holds on to its record for a week and then deletes it for good. A message that is still waiting is never cleared this way, and one that was set aside as undelivered keeps its own separate copy, so it is not affected.
- Delivery rides the same path a normal send uses, fired the instant a turn completes and the session goes idle — so it is reused into a fresh turn and never interrupts a running step.
- That instant can also be a fresh start. If the session has to start its next turn anyway — its saved sign-in was refreshed while it sat idle — the waiting messages go with that start instead of waiting out the turn it begins, so the refresh never costs you a turn's wait.
- A picture on its own queues too. A message that carries only an attachment (a screenshot, pasted text, a file) and no words waits its turn like any other, and its row in the list reads "1 attachment, no text". Before 2026-11-20 such a message was refused with a misleading "Too many messages are already waiting" even when the queue was nearly empty.
- Several waiting messages go over together, in one turn (in order, up to a size cap; whatever does not fit waits for the next one). Every delivery costs the agent a whole turn, so handing it the backlog at once is both faster and better — it can act on the messages knowing what the others say, instead of one at a time.
- You still see them as separate messages. A batch is drawn as one block per message, each tagged with whoever sent it, even though the agent received them as a single message. Messages written hours apart, by different agents, never fuse into one wall of text.
- The agent is told what is in the batch before it reads any of it. A delivery of two or more messages opens with a one-line index naming every one — who sent it, and its summary or opening — so a short message cannot go unnoticed behind a long one. You never see this line: your transcript keeps exactly the messages as you wrote and received them.
- A message queued while a session is still starting up (for example while its working folder is being built) is delivered the moment the session finishes starting and becomes ready. It does not wait for a first turn to end, so messages you type after start-up never jump ahead of it.
- The queue only delivers into a live, idle session. If a session is paused, has errored, or is waiting on capacity, its queued messages simply wait (they never resurrect a closed session); they resume delivering if the session becomes active again. That wait is capped at 24 hours — past that the session has clearly not come back, so the message is set aside as undelivered (findable, never destroyed) rather than waiting forever with nobody told.
- An ended session does not accept a queue at all. Ending is the app's own "nobody is coming back for this" state — unlike pausing, or waiting on capacity, nothing revives an ended session on its own — so a message queued into one would never be read by anybody. Rather than take it and go quiet, the app refuses it and says why, naming the state, so whoever sent it can pick another route. Messages already waiting against a session that ends afterwards are kept — resuming that session still delivers them — and their senders are told they are parked, so they are not waiting on a reply that is not coming.
- Archiving is the same refusal, made permanent — an archived session can never be delivered into, so the app refuses a new message queued for one instead of accepting it and dropping it a moment later, and any queue it was already holding is set aside rather than held forever. Nothing is destroyed silently, and since 2026-09-17 nothing is dropped silently either: each discarded message is preserved as an undelivered one and its sender is told directly.
- A session with messages still waiting does not land in Needs You at that moment. It has not really finished — it is about to take another turn on the next message — so it takes the message straight away and keeps working. The Needs You card appears when it is genuinely done and its queue is empty, so the card you see is a real one that nothing clears out from under you. This includes a turn that ended by asking you a question: the question stays in the session, the queued message is handed over, and if the agent still needs an answer it asks again at the end of that next turn — where the card is a real one and stays. (It used to raise the card and then have the delivery clear it a moment later, so you saw a flash rather than a question.)
- An agent that finishes while messages are queued for it will not archive itself. It was about to sign off without ever seeing them, so the sign-off is held and the queued messages are delivered; the agent can finish properly afterwards. This happens without putting the session in your Needs You — it is not finished, it is about to be handed mail — so there is nothing for you to read or dismiss in between. (Before this, a message queued for an agent that then wrapped up was thrown away at the exact moment it was due to arrive.)
- If a delivery can't go through, it retries on the next idle a few times, then gives up with a visible "couldn't be delivered — you can retype it" note in the session — it never silently vanishes.
- Your normal Enter / Send behavior is unchanged: it still sends now and interrupts a running turn when you want that.
Steer or queue while the agent works
- The setting. Settings → Sessions → "When you send while the agent is working": Queue (the default since 2026-11-05) holds the message until the step finishes, on every engine, with no restart; Steer sends now and ends the current step where the engine allows it, which on Claude stops and restarts the session (a few seconds, and the step in progress is lost). An install that had the old Steer default is moved to Queue once; pick Steer again and it stays.
- The other way. Ctrl+Shift+Enter in the message box does the opposite of the setting while a turn is running.
- What "steer" means here. On Claude, Codex, Gemini, Pi, Devin, Grok, Kimi Code, Hermes and DSH it stops the current step and starts a new turn with your message (a paid restart). On the one-shot engines (Cursor, OpenCode, Antigravity…) the message is queued, and the box says so. No engine takes a message into the running step without stopping it.
- Send now. In the desktop app, while a steerable turn runs, each queued row has a Send now button. It sends that message together with every message queued ahead of it, in order, and ends the current step. It is refused, with the reason, while the session is paused, held, in Do Not Disturb, being restored or rewound, or when the message is too far down to go in one batch. Not available from the phone or web.
Related
A reader of this page usually also wants send-a-message.md, which covers the normal send (Enter) and the interrupt-on-send behavior this is the alternative to, and send-later.md, the sibling that schedules ONE reply for a clock time from the same picker with a different trigger. To hold a whole session for later rather than a single message, see snooze-a-session.md; and for how images and pasted text ride along with a queued message at delivery time, see chat-attachments.md.
Last verified 2026-10-08