Keep working while it builds
In shortA Build request you send while a build runs waits in Up next above the prompt box and starts by itself when the build before it is done — even with the tab closed. Chat and Plan requests don't wait; they answer beside the build. You can move waiting requests up, take one back to edit, remove them, and Stop or Resume the queue.
A build takes a few minutes. You don’t have to wait for it: type your next idea as soon as you have it. MonstarX lines your requests up and works through them one after another, and still answers your questions in the meantime.
What happens when I send a request during a build?
Section titled “What happens when I send a request during a build?”It depends on the mode:
| Request | While a build runs | Hint above the prompt box |
|---|---|---|
| Build (including Edit mode changes, a feature’s Build button and Continue) | Waits in Up next and starts when the build before it is done | Runs when the current build is done or Runs after 2 waiting |
| Chat | Answers right away, beside the build | Answers now, while it builds |
| Plan | Asks its questions right away, beside the build | Asks now, while it builds |
While a build runs, the send button reads Queue for a Build request, and the prompt box says MonstarX is building… add your next request, it runs right after.
Chat and Plan answers also go one at a time among themselves: a second question waits until the first is answered (Runs when the current answer is done).
Builds run one at a time on purpose: your app has one set of files, one preview and one database, so two builds at once would write over each other.
What is Up next?
Section titled “What is Up next?”Up next is the list of waiting requests, right above the prompt box. Each row shows its place in line, an icon for the kind of request (Build, Chat, Plan, Edit mode, QA fix, …), its words and a paperclip if files are attached.
When the build in front finishes, the first request starts by itself. Under it the chat shows Starting… until the reply begins.
How do I change the queue?
Section titled “How do I change the queue?”Hover over a waiting request (or tap it on a phone) to see its buttons:
- ↑ (Run earlier) — moves it up one place.
- ✎ (edit) — takes it out of the queue and back into the prompt box with its words, mode and files, so you can change it and send it again. Edit mode changes and Plan answers can’t be taken back this way; remove them instead.
- × (remove) — takes it out of the queue.
Clear at the top empties the queue. With two or more requests waiting it asks first: click Remove all to confirm or Keep to change your mind. A request that has already started keeps running.
How do I stop MonstarX?
Section titled “How do I stop MonstarX?”Click Stop (the red button in the prompt box). It stops everything MonstarX is doing for this project right now — the build and any Chat or Plan answer — and holds the queue.
Everything written before you pressed Stop is kept, and the stopped request shows Stopped in the chat. If you want to undo it, restore an earlier version.
Why does it say Queue stopped?
Section titled “Why does it say Queue stopped?”The queue pauses whenever something goes wrong, so nothing builds on top of a problem:
- You pressed Stop.
- A build failed.
- Your plan’s usage limit was reached (the limit’s own message says when it resets).
- MonstarX restarted twice in the middle of the same build.
The box turns amber, says Queue stopped and names the reason, for example “Add a newsletter sign-up to the footer” was stopped, so nothing after it has started.
Click Resume to start the next waiting request. Anything you send meanwhile runs straight away as your next step. A failed Chat answer never stops the queue.
Can I close the tab?
Section titled “Can I close the tab?”Yes. Builds run on MonstarX’s servers, not in your browser. Close the tab, lock your phone or open another project: the build carries on, and queued requests start one after another as usual. When you come back, everything that happened is in the chat.
While it works, a note above the prompt box says so — You can close this — MonstarX keeps building. — and offers Notify me, so this device tells you when the build is done or needs you. See Notifications.
How does the queue work with QA?
Section titled “How does the queue work with QA?”Your builds come first:
- If automated QA is testing when you send a build, QA stops and waits. When your queued builds are done it comes back as a choice — Browser QA paused for your build. Run it on the finished app now, or leave it for later. — with Run QA and Later.
- When QA is fixing something it found, that fix goes before your queued builds, because QA diagnosed the app as it is now. The queue says: QA is fixing what it found first; the queued builds run after it.
Frequently asked questions
Section titled “Frequently asked questions”How many requests can wait in the queue?
There is no fixed limit. Each queued build uses credits when it runs, so remove the ones you no longer need.
Can I ask a question while a long build runs?
Yes. Switch to Chat and ask — it answers right away, beside the build. It knows a build is in progress, so a half-finished page is not mistaken for a bug.
Can people I shared the project with change the queue?
People with view access see Up next but not its buttons. Only you (and people who can edit) can queue, reorder, edit or remove requests.
I stopped a build by mistake. How do I carry on?
Send the request again, or click Resume to start the next one in the queue. What was built before you stopped is kept.
Do queued requests start if my usage limit is reached?
No. The queue stops with the limit's message instead of starting builds that could not finish. Click Resume once your limit has reset or after a Boost.