Prompt queueing

Prompt queueing lets you line up follow-up prompts while an agent is still working. Instead of waiting for the agent to finish—or interrupting it to send your next idea—you queue prompts and Warp sends them automatically, one at a time, as each response completes.

The queued prompts panel, with three prompts queued while the agent responds.

Key features

• Auto-queue toggle - Turn on auto-queue so every prompt you submit while the agent is busy joins the queue instead of interrupting the current response.
• /queue slash command - Queue a single follow-up prompt inline, without switching modes.
• Queued prompts panel - View, reorder, edit, and remove every pending prompt from one collapsible panel above the input.
• Automatic sequential sending - Queued prompts fire one at a time as the agent finishes each response, in the order you set.
• Per-conversation queues - Each conversation keeps its own queue and auto-queue state, which persist when you leave and re-enter the conversation.
• Cloud agent support - Queue follow-ups for cloud agents, even while the environment is still setting up.

How it works

Each agent conversation has its own queue. When the current response finishes successfully, Warp sends the next prompt in the queue. This continues one prompt at a time until the queue is empty.

Queued prompts use the same submission flow as prompts you send manually, so slash commands, skills, and other input behave the same way.

A few things to know:

• Shell commands are never queued. If you submit in shell mode, Warp runs the command in the terminal immediately, regardless of your auto-queue setting.
• Queues don’t persist across restarts. A conversation’s queue is cleared when the conversation is deleted or cleared, and queues do not persist after an app restart.
• One prompt is in flight at a time. Warp waits for the current response to finish before sending the next queued prompt.

Queueing a prompt

There are three ways to queue prompts. The auto-queue toggle and /queue act on the active conversation; the default submission mode setting controls what happens app-wide.

Auto-queue toggle

The auto-queue toggle is the fastest way to queue several prompts in a row. While the agent is responding, a clock-plus icon appears in the warping indicator (the status bar above the input).

The auto-queue toggle in the warping indicator.

1. Click the clock-plus icon, or press ⌘+Shift+J (macOS) or Ctrl+Shift+J (Windows/Linux). The icon turns the accent color to show auto-queue is on.
2. Type a prompt and press Enter. Because the conversation is in progress, the prompt is added to the queue instead of interrupting the current response. The input refocuses so you can keep queuing.

The toggle is per-conversation and stays on across responses until you turn it off, so you can queue as many prompts as you like. Switching to another conversation shows that conversation’s own toggle state.

/queue slash command

Use /queue to add one follow-up prompt without turning on auto-queue.

1. In an agent conversation, type /queue followed by the prompt—for example, /queue run the tests and fix any failures.
2. Press Enter. The prompt is added to the queue and the input clears.

/queue requires an active conversation and a prompt. If you run /queue without a prompt, Warp shows an error.

Note: If the agent is idle, /queue sends the prompt immediately. It only queues prompts while a response is in progress.

Set the default submission mode

By default, submitting a prompt while the agent is responding interrupts the current response and sends your new prompt right away. You can change this default so new conversations queue instead.

1. In the Warp app, go to Settings > Agents > Warp Agent > Input.
2. For Default prompt submission mode, choose one of:
   • Interrupt response - Cancel the in-flight response and send the new prompt immediately (the default).
   • Queue until response finishes - Hold the new prompt until the current response finishes, then send it.

This setting is the default for conversations that you haven’t explicitly toggled. The per-conversation auto-queue toggle always overrides it for that conversation.

The Default prompt submission mode setting under Agent input settings.

Managing queued prompts

When a conversation has at least one queued prompt, the queued prompts panel appears between the warping indicator and the input box. Its header shows the count, such as 2 queued, with a chevron to collapse or expand the list. The panel is expanded by default, and prompts are listed from top (next to send) to bottom (last to send).

Hovering a row reveals controls for that prompt:

• Reorder - Drag a row up or down by its handle to change the order. The row at the top of the list always sends next.
• Send now - Click the up-arrow icon to send that prompt immediately instead of waiting for the agent to finish the current response.
• Edit - Click the pencil icon to edit the prompt inline. Press Enter to save your changes or Esc to cancel.
• Delete - Click the trash icon to remove the prompt from the queue. If the input is empty, Warp moves the deleted prompt into the input so you can revise and resend it. If the input already has text, the deleted prompt is discarded.

A queued row with its send now, edit, and delete controls revealed on hover.

Deleting the last prompt removes the panel, since the queue is now empty.

When sending pauses

Queued prompts only continue after a response finishes successfully. If the response errors, is stopped, or is interrupted with Ctrl+C, Warp pauses the queue so you can review what should happen next. The queue stays intact, and no queued prompts are discarded.

When sending pauses and you’re viewing that conversation, Warp helps you pick up where you left off:

• If the input box is empty, the first queued prompt is removed from the queue and its text is placed in the input so you can review and resend it.
• If the input box already has text, the queue is left untouched.

Any remaining prompts stay in the panel so you can review, edit, reorder, or delete them. Sending resumes automatically the next time the conversation completes a response cleanly.

Prompt queueing with cloud agents

Prompt queueing also works for cloud agents, including while a cloud environment is still setting up. You can queue follow-up work before the agent is live, and Warp sends those prompts once the agent is ready and the current response finishes.

For cloud agents, the prompt that started the run appears as a locked first row in the queue because it has already been accepted by the agent. You can’t edit, reorder, or delete that first prompt, but any follow-up prompts queued behind it remain editable.

A cloud run’s locked initial prompt during environment setup.

While the environment is setting up, queued prompts wait until the cloud agent is live. After setup, the locked row is removed and the rest of the queue sends in order as each response completes.

Because cloud conversations keep running after you leave the agent view, their queues continue to send in the background and are restored when you return.

Related pages

• Slash Commands - The full list of built-in commands, including /queue.
• Terminal and Agent modes - How input is routed between the terminal and the agent.
• Cloud agents overview - Run agents in the cloud from any trigger.