Queue Drawer
The Queue Drawer holds messages you’ve sent to busy agents and delivers them in order once each agent becomes idle, with drag-reorder and delete controls so you can adjust priorities on the fly.
How It Works
Section titled “How It Works”When an agent is mid-reply and you send another message, that message doesn’t drop or interrupt — it goes into the agent’s Queue. Each agent has its own queue, ordered first-in-first-out, with a cap of 200 messages per agent. As soon as the agent finishes its current turn and goes idle, the queue head is delivered automatically and the agent starts processing it.
The HudShelf along the bottom of the screen carries a queue strip that shows a compact list of agents with non-empty queues, each with a pill summarizing depth and the next message preview. Click a pill, or click the Queue button in the HudShelf, to open the full Queue Drawer. The drawer is a wider panel that lists every queued message for every agent with controls for reordering and deletion.
Inside the drawer, each agent has its own section. Within an agent’s section, every queued message is a row showing the message text (truncated), the time you sent it, and a delete button. Drag a row up or down within its section to reorder — the queue stays first-in-first-out, but reordering changes which message goes first. Click delete to remove a message before it’s delivered.
Closing the Queue Drawer doesn’t pause delivery. The queue keeps draining in the background. Messages that have already been delivered to the agent don’t reappear; only the still-pending ones are visible.
UI Indicators
Section titled “UI Indicators”- Queue strip in the HudShelf — a horizontal row of pills, one per agent with a non-empty queue.
- Pill badge on each agent’s pill shows the queue depth (number of pending messages).
- Hover tooltip on a pill previews the next message text and the time stamp.
- Drawer open transition slides the Queue Drawer up from the HudShelf.
- Drag handle appears at the left of each message row in the drawer.
- Delete button — a small trash icon at the right of each row.
- Cap warning — when an agent’s queue is near 200 messages, the pill turns a warning color and further sends are rejected.
- Empty state — agents with no pending messages don’t appear in either the strip or the drawer.
Use Cases
Section titled “Use Cases”- Pipeline a sequence of follow-ups. Send a request to a Developer, then queue the next two prompts (“now add tests”, “now write docs”) so they fire automatically when the first turn finishes.
- Reorder priorities. Drag a queued message to the top of an agent’s section if you change your mind about what should happen first.
- Cancel something you regret. Delete a queued message before the agent gets to it.
- Run a batch across multiple agents. Queue messages to each member of a CodeForge or MarketResearchers team and walk away — every agent drains its own queue independently.
- Peek at backlog at a glance. Read the queue strip in the HudShelf to see which agents are still working through pending work.
Limitations
Section titled “Limitations”- The cap is 200 messages per agent. Once full, additional sends to that agent are rejected; deliver or delete some queued items before sending more.
- Reordering only changes the order of pending messages. The message currently being processed is already in the agent’s hands and can’t be pulled back from the queue.
- The queue is per agent; there’s no global queue across agents. Reordering across agents isn’t supported.
- Deleted messages are gone — there’s no undo. If you delete the wrong one, retype and re-send it.
- Queues survive app restarts. If you quit Viberia with messages still queued, they’ll deliver when you next launch.