Message Queue
Send the next message before the current turn finishes — the queue drains automatically.
What is the queue?
While the agent is working on a message, you can already type and submit the next one — it lands in a queue instead of bouncing the input. As soon as the current turn finishes, the head of the queue is dispatched as the next turn automatically.
Header & states
When at least one message is queued, a thin pill appears above the chat input:
Queue [3] ⏸ ⌄- Counter — how many messages are waiting
- Pause / Play — stops auto-drain without losing the queue
- Chevron — expands the list
Empty queue hides the pill entirely so the chat stays calm.
Expanded list
Clicking the chevron expands the queue. Each entry shows:
- A drag handle (six dots) — drag to reorder
- A position number
· 01,· 02, … in monospace - The message text (truncated)
- An
als nächstes/next uppill on the first entry (only when not paused) - A small × to remove
Auto-drain
The moment isGenerating flips back to false (turn ended), the queue's head is popped and sent as the next message — unless you've paused. Resume after a pause also drains immediately. Reordering takes effect on the next drain, so you can promote a later message to run first.
When to use it
The queue is built for the rhythm of building features: type the next step while the agent is finishing the current one. You don't have to wait for completion to describe what comes after. Pausing is useful when you've queued speculative work and want to review the result of the current turn before more changes go through.