add docs for prompt queueing#172
Open
harryalbert wants to merge 2 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR adds a new Prompt Queueing documentation page, links it from the local-agent interaction docs, adds /queue to the slash command reference, and includes the new page in the sidebar. The docs cover the feature behavior, settings, queue management, cloud-agent behavior, and related pages.
Concerns
- One title-casing style issue is called out inline; no correctness, security, or spec-alignment blockers were found.
Verdict
Found: 0 critical, 0 important, 1 suggestions
Approve with nits
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
harryalbert
force-pushed
the
harry/prompt-queueing-docs
branch
from
7f0803d to
26e7b86
Compare
hongyi-chen
approved these changes
Jun 3, 2026
Collaborator
hongyi-chen
left a comment
hongyi-chen
left a comment
There was a problem hiding this comment.
left some copy suggestions, but ty for putting this together! the screenshots help a lot!
Comment on lines
+24
to
+34
| ## How it works | ||
|
|
||
| A queue belongs to a single conversation. When that conversation finishes a response cleanly, Warp removes the first prompt from the queue and submits it as the next prompt in the same conversation. The remaining prompts stay queued and the panel updates its count. This repeats until the queue is empty. | ||
|
|
||
| Queued prompts run through the normal submission path, so slash commands, skills, and other input behave exactly as they would if you had typed and sent the prompt yourself. | ||
|
|
||
| A few boundaries apply: | ||
|
|
||
| * **Shell commands are never queued.** Submitting in shell mode runs the command in the terminal immediately, regardless of your auto-queue setting. | ||
| * **Queues don't persist across restarts.** A conversation's queue is dropped when the conversation is deleted or cleared, and queues do not survive an app restart. | ||
| * **One prompt is in flight at a time.** Queued prompts wait for the current response to finish before the next one sends. |
Collaborator
There was a problem hiding this comment.
Suggested change
| ## How it works | |
| A queue belongs to a single conversation. When that conversation finishes a response cleanly, Warp removes the first prompt from the queue and submits it as the next prompt in the same conversation. The remaining prompts stay queued and the panel updates its count. This repeats until the queue is empty. | |
| Queued prompts run through the normal submission path, so slash commands, skills, and other input behave exactly as they would if you had typed and sent the prompt yourself. | |
| A few boundaries apply: | |
| * **Shell commands are never queued.** Submitting in shell mode runs the command in the terminal immediately, regardless of your auto-queue setting. | |
| * **Queues don't persist across restarts.** A conversation's queue is dropped when the conversation is deleted or cleared, and queues do not survive an app restart. | |
| * **One prompt is in flight at a time.** Queued prompts wait for the current response to finish before the next one sends. | |
| ## 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. |
|
|
||
| ## When sending pauses | ||
|
|
||
| Queued prompts only advance after a clean completion. If the active conversation finishes for any other reason—an error, or you stop it with the stop button or `Ctrl+C`—auto-fire pauses and the queue is left intact rather than flushed. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Queued prompts only advance after a clean completion. If the active conversation finishes for any other reason—an error, or you stop it with the stop button or `Ctrl+C`—auto-fire pauses and the queue is left intact rather than flushed. | |
| 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. |
| * **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 box is empty, the deleted prompt's text is placed into the input so you can revise and resend it; if the input already has text, the deleted prompt is discarded. |
Collaborator
There was a problem hiding this comment.
Suggested change
| * **Delete** - Click the trash icon to remove the prompt from the queue. If the input box is empty, the deleted prompt's text is placed into the input so you can revise and resend it; if the input already has text, the deleted prompt is discarded. | |
| * **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. |
|
|
||
| ### `/queue` slash command | ||
|
|
||
| Use `/queue` to add a single prompt without turning on auto-queue. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Use `/queue` to add a single prompt without turning on auto-queue. | |
| 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 argument; running `/queue` with no prompt shows an error. If the agent is idle (no response in progress), `/queue` sends the prompt immediately instead of queuing it. |
Collaborator
There was a problem hiding this comment.
Suggested change
| `/queue` requires an active conversation and a prompt argument; running `/queue` with no prompt shows an error. If the agent is idle (no response in progress), `/queue` sends the prompt immediately instead of queuing it. | |
| `/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. |
|
|
||
| ## Prompt queueing with cloud agents | ||
|
|
||
| Prompt queueing also works for [cloud agents](/agent-platform/cloud-agents/overview/), including while a cloud environment is still setting up. Submitting a prompt during setup adds it to the queue instead of doing nothing, so you can stack up follow-up work before the agent is even live. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Prompt queueing also works for [cloud agents](/agent-platform/cloud-agents/overview/), including while a cloud environment is still setting up. Submitting a prompt during setup adds it to the queue instead of doing nothing, so you can stack up follow-up work before the agent is even live. | |
| Prompt queueing also works for [cloud agents](/agent-platform/cloud-agents/overview/), 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. |
|
|
||
| Prompt queueing also works for [cloud agents](/agent-platform/cloud-agents/overview/), including while a cloud environment is still setting up. Submitting a prompt during setup adds it to the queue instead of doing nothing, so you can stack up follow-up work before the agent is even live. | ||
|
|
||
| The prompt that started the cloud run appears as a locked first row in the panel. You can't edit, reorder, or delete it because the cloud agent has already accepted it—hovering its controls shows the tooltip "The first cloud-mode prompt cannot be changed." Any follow-ups you queue behind it remain fully editable. |
Collaborator
There was a problem hiding this comment.
Suggested change
| The prompt that started the cloud run appears as a locked first row in the panel. You can't edit, reorder, or delete it because the cloud agent has already accepted it—hovering its controls shows the tooltip "The first cloud-mode prompt cannot be changed." Any follow-ups you queue behind it remain fully editable. | |
| 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. |
| <figcaption>A cloud run's locked initial prompt during environment setup.</figcaption> | ||
| </figure> | ||
|
|
||
| While the environment is still setting up, the send-now control is disabled for every row—queued prompts can't be sent until the cloud agent is live. Once the cloud agent picks up the initial prompt, the locked row is removed and the rest of the queue drains in order as the agent finishes each response. 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. |
Collaborator
There was a problem hiding this comment.
Suggested change
| While the environment is still setting up, the send-now control is disabled for every row—queued prompts can't be sent until the cloud agent is live. Once the cloud agent picks up the initial prompt, the locked row is removed and the rest of the queue drains in order as the agent finishes each response. 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. | |
| 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
We're releasing prompt queueing to stable this week, so we should have docs that explain the feature and how to use it.