Queue instructions during a run

While you are driving an active chat, use Queue message below the conversation. Write the additional instruction and submit it. The queue shows its status, and teammates can see the queued work.

You can remove a message before the executor claims it. Once claimed, it may already be reaching the AI tool. Only the current driver with edit access can send or cancel queued instructions.

Codex: the integration can steer its active app-server turn. The tool decides when the instruction is consumed; it cannot retroactively change a command already executing. If the response has just finished, the instruction may start another turn.

Other supported CLI providers: queued instructions wait until the current process finishes and then run in order with prior conversation context. The interface describes this as queued for the next response.

A delivery acknowledgement means the instruction was submitted, not that the requested result has been achieved.

If a task fails or is recovered after a disconnect, a queued instruction may be marked failed or unconfirmed. Inspect the transcript and saved activity before resending. Unconfirmed messages are not automatically replayed because they might already have affected the work.

If the turn finishes while you submit, the app may reject the late instruction and preserve your draft. Send it as a normal next prompt after reviewing the completed result.