ChanTan Studio DocsHow to Queue Several Requests in ChanTan Studio
Write your next request while ChanTan is still busy — it waits in a queue instead of being lost. Why the queue starts paused, and how to reorder or clear it.
You don't have to wait for a build to finish before writing your next idea. Type it and send it — it joins a waiting list and runs when the current work is done.
Nothing you send is ever lost, and nothing interrupts work already running.
1. Send a message while ChanTan is busy
Type as normal. The send button shows an amber list icon — "Queue message" — telling you your message will wait rather than send now.
2. Find the queue strip
A strip appears above the message box listing every waiting message as a numbered row.
Each row shows a "PLAN" or "BUILD" badge, and a 📎 count if it carries attachments.
3. Press the green "Play" button
This is the step everyone misses. The queue always starts paused.
The status chip reads "Paused — waiting for you". Press the green "Play" button and your messages run one after another, in the order you see them.
Its tooltip says: "Run the queued messages in order".
4. Watch them run in order
While running, the chip reads "Running — next up after this", and the count shows how many are still waiting ("{n} queued").
✅ Done! Each queued request becomes its own reply in the chat, one after another, until the strip is empty and disappears.
Rearranging, editing and removing
| Control | What it does |
|---|---|
| Grip handle | Drag a row onto another to reorder |
| ▲ / ▼ | "Move up" / "Move down" |
| ✏️ pencil | "Edit — put this back in the composer" — takes it out of the queue and back into your text box so you can change it |
| ✕ | "Remove" — deletes that one |
| "Clear all" | Empties the queue |
On a phone these controls are always visible; on a computer they appear when you hover a row.
Pausing
"Pause" means "Pause — the current run finishes, the next one waits". It never cuts off work in progress.
Pressing Stop on a running build also pauses the queue — it never deletes it. Your waiting messages stay exactly where they are until you press Play again.
What each queued message costs
Each queued request is billed as its own run when it executes, exactly as if you'd sent it on its own. Queuing itself costs nothing.
Good things to queue
Queue steps that build on each other, in the order you want them:
- "add an About page"
- "put a link to About in the header"
- "add a contact form at the bottom of About"
Then press Play once and walk away.
If something goes wrong
| What you see | What to do |
|---|---|
| Nothing is running and the chip says "Paused — waiting for you" | Press the green "Play" button — the queue always starts paused |
| Your queued photos vanished after a page refresh | Re-attach them with ➕, then press Play. Only the text survives a refresh |
| "Another run is still working — try again when it finishes." after approving a plan | Wait for the current run and approve again. This is deliberate, so a plan can't be built twice |
| The queue reappeared paused after a reload | That's on purpose — reloading can never fire off old work by itself |
Honest limits
⚠️ Photos and files attached to a queued message are not kept across a page refresh. The text comes back; the attachments don't. Re-attach them before pressing Play.
- Buttons on ChanTan's own cards never queue. Approving a plan or connecting a database acts immediately on the card in front of you.
- A second browser tab never sees or re-sends the first tab's queue.
- Queued messages run one at a time. If a later message depends on an earlier one going well, check the result before pressing Play again — you can always Pause between steps.