Message Queue

  • Desktop, mobile and web
  • All plans
View as MarkdownFeature page

What it does

Instead of sending every prompt right away, you stack messages above an agent's composer and send them one at a time, in the order you choose, so the agent gets one clear task at a time and you keep a view of what is still to come. Each queued card keeps its text, screenshots and dropped files, and gets a short title summarized by AI. A card can also carry a clock: it then leaves on its own at a time you pick, or on your AI subscription's quota window (when the quota comes back, or shortly before it resets once the plan is consumed past a threshold). The phone can stack a card, arm one with a clock, or send a waiting card now; the desktop holds the queue and sends.

Video (1 min 15): Message Queue, shown in the real app. Three requests are parked in the queue with Add to queue, then sent to a real agent one card at a time: a bug fix, a test, a changelog entry.

Where to find it

  • In an agent's composer, once you have typed something or attached a file: the Add to queue button next to Send, and Send later to stage the message with a timer.
  • Queued cards sit right above the composer of that agent. Send all appears above the stack as soon as two cards are queued; Collapse joins it from three cards.
  • Each project tile on the projects home shows how many prompts are still waiting on its agents.
  • Mobile: the clock button next to send opens the Send later sheet, whose first row is Add to queue, followed by the time presets, the exact time and Quota timing. The agent's cards sit above the composer in the desktop order, each with Send now and Remove from queue.
  • The small button at the top right of the input box, next to Expand (Hide the input box), hides the composer in one click; the round button at the bottom right of the pane brings it back (Show the input box).

How to use it

  1. Write a message, click Add to queue. The card appears above the composer and the composer clears. Repeat for each idea.
  2. Drag a card to reorder (Drag to reorder), click it to reopen it in the composer (Open to edit; whatever was in the composer goes back to the queue first), use Send now or Remove from queue.
  3. Send all sends the whole queue as a single message, cards in order and separated by a horizontal rule (a markdown --- line), so the agent sees where one message ends and the next begins. The queue is then empty. When you re-read that message in the desktop Conversation view, each card is its own block under a thin rule, and since 2026-09-17 the screenshots and files of a card sit under that card's block rather than all together at the end of the bubble.

Collapse (since 1.176.0): from three cards, the actions row also offers Collapse ("Hide the queued cards so the terminal stays readable"). The stack folds away and only the actions row remains: Send all with its card count, a clock chip with the number of hidden scheduled cards (hover it: "2 scheduled messages are hidden in the collapsed queue") and Expand ("Show the queued cards again"). The fold is not saved: a queue you come back to after a restart is always expanded, and it unfolds by itself when the queue drops below three cards.

Send later: click Send later (or the clock on a card, "Send this one later"). Pick In 15 min, In 30 min, In 1 h, In 2 h, In 4 h, Tomorrow, or type an exact time under or at (today if still ahead, tomorrow otherwise), then Set. The chip shows a live countdown ("in 58 min", "at 21:30"); click it to reschedule or Remove the timer.

Quota timing: in the same popover, When quota returns fires at the reset of the chosen Quota window (5-hour, Daily, Weekly, Monthly); Before reset fires Send before reset (30 min, 1 h, 2 h, 4 h) ahead of the reset, only once Minimum used (Any usage, 50%, 80%, 90%) is reached; below that the card waits for the next window.

Settings

None.

Agent tools (MCP)

None. The queue is a surface for the human; agents receive the messages as ordinary prompts.

Providers

All providers, no difference. Quota timing only offers the windows for which AgentsRoom can name an exact reset moment: either a structured source (the Claude quota API, the Codex usage API or its last session snapshot, the Grok, Cursor, Kimi and OpenCode usage APIs, Antigravity's agy /usage) or the reset sentence printed in the CLI's own usage panel, now read back into a date for Kimi and Grok as well ("resets in 2h 8m", "August 3, 15:52", "7pm (Europe/Paris)"). The reading is deliberately strict: an unknown wording, an ambiguous hour or a timezone other than the machine's produces no date at all, because arming a message on a boundary that does not exist is worse than offering nothing. When nothing can be resolved the popover says "No quota window with a known reset is available for this agent yet".

Mobile

Present. Scheduling has been on the phone for a while; since 2026-09-15 the phone also stacks and sends plain cards. Write a message, tap the clock, then Add to queue ("Add this message to the queue to send it later, in your order"): the card joins the agent's queue on the desktop, and the strip above the phone composer shows every card of that agent in the desktop order, with its rank ("#2 in queue") or its countdown. Send now on a card asks the desktop to send it right away (an unreachable agent gives the usual "waiting for the agent" retry, nothing is lost); Remove from queue drops it. Scheduling is unchanged: the same time presets, exact time, quota windows, leads and thresholds, with the desktop holding the timer and pushing "Scheduled message sent" once out. From three cards the strip also offers Collapse, with the same threshold and the same words as the desktop: folded, a single line remains, "3 in queue" plus Expand. Not on the phone, on purpose: drag to reorder, reopening a card in the composer, Send all, and attachments (a card stacked from the phone is text only; "Attachments cannot be scheduled"). The phone's send button still goes straight to the live composer. If the desktop is unreachable, nothing is queued and the text stays in the phone composer.

Limits

  • The queue is per agent and saved locally on the desktop; it survives restarts but does not sync between machines.
  • Timers run on the desktop while AgentsRoom is open. A message whose time passed while the app was closed goes out on the first check after reopening.
  • If the agent is unreachable when the time comes, the card stays marked "waiting for the agent", AgentsRoom starts that agent and retries; nothing is dropped.
  • No full date picker, on purpose: a message for next week is a backlog ticket, recurring work is a scheduled task.
  • Quota precision is that of the usage scan (around 10 to 30 minutes), not the minute.
  • The AI title is best-effort: offline, the card shows the first line of the text.

Common questions

  • Do queued messages send automatically? Only the ones you armed with a time or a quota rule. Everything else waits for your click.
  • A message sent from my phone, or a scheduled one, stayed "waiting for the agent" on a Codex agent under Windows that was clearly ready. Fixed on 2026-09-27: AgentsRoom no longer waits for a start-up signal Windows does not always produce; an agent idle at its prompt is recognised as ready, for every CLI. Update the desktop.
  • Can I queue screenshots? Yes, attachments stay on the card and go out with it.
  • What is the difference with a scheduled task on the quota? Lifetime. A quota-armed message is a one-shot: it leaves once and the card is gone. A quota frequency on a scheduled task fires again on every window.
  • Does reopening a scheduled card disarm it? No, editing keeps the timer.
  • Can I add to the queue from my phone? Yes: clock button, then Add to queue. The card lands in the desktop queue; tap Send now on it later, or let the desktop send it when you click there.
  • How does the agent tell queued messages apart in a Send all? Each message is separated from the next by a horizontal rule. In the desktop Conversation view you see the same split: one block per card, with its own attachments under it.
  • The queue hides the terminal, can I fold it? Yes, from three cards click Collapse in the row above the stack; Send all and the count of hidden scheduled cards stay visible, Expand brings the cards back. The fold is forgotten on restart.
  • Can I hide the input box quickly? Yes, the small button next to Expand at the top right of the box hides it; the round button at the bottom right of the pane shows it again.
  • Is there a video that shows it? Yes, a little over a minute, filmed in the real app: https://youtu.be/QvA4UiZGJ4E

Related