You know the moment. The build is running, the preview is filling in, and your next idea is already forming. Until today, that idea waited on a spinner.
Prompt queueing ends the wait. Type your next prompt while Bolt.new is still building, hit Enter, and it joins the queue. When the current build finishes, the next prompt fires on its own. Your fifth idea can be in line before your first one finishes building.
Prompt queueing is live in every Bolt.new project, for everyone, starting today:
- Type your next prompt while a build runs. It joins the line and fires in order.
- Drag to reorder, edit or delete your own prompts, stop everything with one click, and resume when you're ready.
- A failed prompt keeps its retry button. You decide when the line moves again.
- Teammates on a project see the same queue in real time and add to it together.
- Each queued prompt remembers the agent you picked for it, so a standard-agent prompt and a max-agent prompt can wait in the same line.
What is prompt queueing?
Prompt queueing lets you send prompts to Bolt.new while it's still working on the last one. Instead of blocking the input until the build finishes, Bolt.new holds your prompts in an ordered queue and runs each one when its turn comes. You think at your speed; the builds happen at theirs. It's live in every Bolt.new project as of August 2026.
How does the prompt queue work?
Type your next prompt mid-build and send it. That's the whole workflow. The queue shows your next five prompts at a glance and scrolls to hold as many as you can think up.
Here's what you can do with a queued prompt, and whose prompts each control touches:
| Control | How | Applies to |
|---|---|---|
| Reorder | Drag prompts up or down the line | Any prompt in the queue |
| Edit | Open it, rewrite, confirm (confirming never sends it early) | Your own prompts |
| Delete | Remove it before it runs | Your own prompts |
| Stop | Stop the current response; the queue pauses with it | The whole queue |
| Resume | One button restarts the line where it left off | The whole queue |
One more behavior worth knowing: settings travel with each prompt. Queue one prompt on the standard agent and the next on max; each runs with the setup it was sent with.
Version history plays nice with the queue: stop the queue, restore the version, and pick the line back up. Your queued prompts survive the trip, still yours to edit, reorder, or run.
What happens if a build fails mid-queue?
The failed prompt doesn't vanish, and neither does your plan. The prompt keeps its retry button, and the queue stays under your control: stop the line, fix or retry the failed step, reorder what's left, and resume when the build is back on track.
Queued prompts often build on each other ("create the page," then "style it"), so when one errors out, it's worth checking the result before the dependent prompts run. Stopping the queue is one click, and everything in it waits for you.
Is the prompt queue multiplayer?
Yes. Everyone collaborating on a project shares one queue and sees it update in real time. Your teammate can line up the next three prompts while you watch the current build, and the queue runs everyone's prompts in order.
Each person manages their own contributions: you can edit or delete your own queued prompts, and a teammate's prompts are theirs. If someone closes their tab with prompts still in line, their prompts wait for them to return while everyone else's keep flowing. Nobody's coffee break blocks the team.
Why queueing changes how you build
The rhythm of building with AI has always had a gap in it: prompt, wait, prompt, wait. The waits were where ideas went to evaporate. Prompt queueing closes the gap. Sketch the whole feature as a series of prompts, then review the results as they land. It turns a chat into a plan.
Your thoughts shouldn't have to wait their turn.
Try it
Prompt queueing is live in every Bolt.new project now. Open a project, start a build, and type what's next.
