Warp: Prompt Queueing for Uninterrupted Agent Workflows
WarpWarp has shipped prompt queueing to its stable channel, allowing users to submit multiple follow-up prompts while the agent is actively working on a task. Users can activate queueing through a chip in the warping line, the /queue slash command, or a new default setting called "Queue until response finishes." A dedicated "Send Now" button on each queued prompt lets users bypass the queue instantly when needed.
Sources & Mentions
1 external resource covering this update
Prompt Queueing Comes to Warp Stable
One of the most-requested workflow improvements has landed in Warp's stable channel with the v0.2026.06.03 release: prompt queueing. Users no longer need to wait for an agent to complete its current task before sending the next instruction. Multiple follow-up prompts can now be composed and queued, ready to execute the moment the agent finishes what it is working on.
Three Ways to Queue Prompts
Warp offers three activation modes, giving users flexibility based on their workflow style:
Queueing mode chip. A new chip appears in the warping line, the status indicator shown while an agent is actively running. Activating the chip switches the current conversation into queueing mode so that any prompt submitted before the agent finishes is held in the queue rather than interrupting execution.
The /queue slash command. Users can prefix any individual prompt with /queue to explicitly enqueue it as a one-off action, without committing to queueing mode for the entire conversation. This is useful for users who generally prefer the default interrupt behavior but want to queue a specific follow-up.
Default behavior setting. A new option called "Queue until response finishes" appears in Warp's settings. Once enabled, every prompt sent while an agent is working is automatically queued for all new conversations. Users who prefer the previous interrupt behavior can leave this off and rely on the per-conversation chip or slash command instead.
The "Send Now" Button
Each queued prompt now surfaces a "Send Now" button, which immediately delivers that message to the agent regardless of queue position. This is useful when a user realizes a queued instruction is more urgent than anticipated. The button is intentionally disabled during cloud environment setup, since no prompts can be sent until the environment is fully initialized.
Why This Matters
Before this release, submitting a prompt while Warp's agent was running would interrupt its current task, forcing a stop-and-start pattern: wait for completion, then submit the next instruction. For longer-running tasks (code generation, multi-file refactors, test runs) this was a meaningful friction point. Users working through a sequence of tasks had to context-switch back to Warp to issue each instruction after the previous one completed.
Prompt queueing closes a gap with competing agentic development environments, particularly Claude Code and Cursor, where queuing has been available for some time. For users running multi-step coding workflows in Warp, the ability to front-load a sequence of instructions and let the agent work through them without interruption meaningfully reduces the overhead of managing agent sessions.
Bug Fixes and Stability Improvements
The June 3 release also includes reliability fixes:
- Fixed a crash when accessing the microphone on macOS
- Resolved orchestration session restoration after Warp restart
- Fixed symlinked gitignored paths being incorrectly included in code review diffs
- Fixed a logic error causing unnecessary repeated SVG rasterization
- Resolved conversation creator profile display inconsistencies
- Improved queued prompt hover behavior and drag handle interactions
- Fixed a billing UI displaying a misleading per-row base-limit denominator