Skip to main content
A chat runs one turn at a time. Everything else waits in a queue that you can see and edit. The queue has two lanes.

Send while the agent works

Press Enter while a turn is running. The message appears in the chat with an Up next badge and runs as soon as the current turn settles. The agent reads the queue before it continues, and it reconciles queued work that your new message makes stale. It can edit, remove, or reorder its own queued rows. It never touches your messages.

Add to queue

Press Alt+Enter (Option+Enter) or click Add to queue. The message goes to the queued work lane. Use this for follow-ups that must wait for the current result, such as “then export everything as a zip”.

The queue drawer

The queue drawer sits behind the composer and lists Queued requests. It rises as rows are added. For each row you can:
  • Drag it to reorder, or use move up and move down.
  • Edit its text.
  • Cancel it.
A separator, Runs after your requests, marks where your pending messages end and queued work begins. Each row shows a phase. Waiting for source means the row needs a previous run to land. Approval waiting means a checkpoint blocks it. Chain halted means you stopped the chain. Ready rows dispatch next.

Plan steps in the queue

When a plan runs, every remaining step becomes a queue row. Removing a step removes the steps that depend on it. Approval checkpoints hold their row until you approve.

Stop

The send button becomes a stop button while a turn runs. Escape triggers it. Press Escape twice to confirm. Stop escalates in two presses:
  1. Halt the chain. Queued rows stay in the drawer but do not dispatch. Continuations from landed runs wait.
  2. Cancel generations. In-flight runs are cancelled. Their cells show Cancelled. Dependent rows are parked with Source run stopped rather than deleted.
To resume a halted chain, send a message or click resume in the drawer. Resume clears the halt on every waiting row at once.

Cancel one generation

Hover an in-flight cell and click the cancel button. Only that run stops. The rest of the batch continues.

Cost approvals

A run that exceeds your spending cap waits for approval. While it waits, the agent cannot submit more runs in that chat. Approve or reject it in the chat.