Message queue
Line up your next requests while Modulify is still working on the last one.
On this page
You do not have to wait for a build to finish before typing the next thing. Send a message while a run is in progress and it joins a queue, which drains in order as soon as the current run ends.
The queue is shared with everyone in the project, so you can see what a teammate lined up and they can see yours.
Queue a message
Write and send exactly as normal. When a run is active, or the queue already has something in it, the message goes to the queue instead of starting a run.
A panel appears above the chat box headed Queued with a count badge. Click the header to collapse and expand it.
You cannot queue a message whose attachments are still uploading. That raises Attachment still uploading and asks you to wait for the upload to finish.
Read the queue
Each row shows the author's avatar and the first 140 characters of the message, with attachment and element chips rendered inline exactly as you wrote them.
Extras appear on the right of a row:
- A red
Runtime error,Build errororLogbadge for each error chip the message carries. 3 filesfor attachments that were not placed inline in the text.- The model name, if the message was queued on a different model from the one the picker shows now.
- The mode name, if it was queued in a different mode.
A message with no text but with files reads Attached files.
Reorder
Drag the handle on the left of a row to move it. The handle only becomes active when there is more than one message in the queue. Reordering applies for everyone.
The row menu
Hover a row and a three dots menu appears with three entries.
- Edit loads the message back into the chat box, chips and all, and switches the mode and model pickers to whatever it was queued with. Only the author can edit their own message, so the entry is disabled on a teammate's.
- Copy puts the message text on your clipboard.
- Remove deletes it before it runs.
Remove asks first. The confirmation names whose message it is and warns that its attached files will be deleted too. Removing applies for everyone, and it cannot be undone.
While editing
An Editing pill appears on the row being edited, and a Cancel edit button appears in the panel header. The send button turns into a checkmark, because pressing it commits the edit rather than sending a new message.
Cancel edit restores whatever was in your chat box before you started.
The limits
The queue holds 20 messages in total and 8 from any one person. Hitting either raises a toast, Queue is full or You have queued enough, and asks you to remove one before adding another. The count badge turns red when the queue is full.
When the queue pauses
The queue drains on its own in most cases. It stops and waits in three that need you, and the panel shows a line explaining which.
| The panel says | What to do |
|---|---|
Paused because the last run was stopped. |
Click Run queue |
Paused because the last run failed. |
Fix or acknowledge the problem, then click Run queue |
Paused because the workspace is out of credits. |
Top up or upgrade, then the queue resumes |
The Run queue button appears next to the message for the first two. This is deliberate: after a stop or a failure, running the rest of the line blindly is usually the wrong thing, so somebody has to say go.
The queue also holds quietly while a run is in flight, while a question is waiting for your answer, and while a plan is waiting for approval. Those clear themselves as soon as you answer, so no button appears.
What each message keeps
A queued message carries its own mode, model, effort, attachments, skills and connectors, frozen at the moment you queued it. Changing the pickers afterwards does not change anything already in the queue, which is why the row shows a badge when they differ.
Each message also runs as its author. If the author has left the workspace by the time their message reaches the front, it is dropped rather than run.
Sending with no credits
Running out of credits does not queue new messages. Pressing send opens the top up or upgrade flow instead. Only messages already in the queue when the balance hit zero are held.
Next
- Plan and Build modes covers the approval step that holds a queue.
- Models and effort explains the settings each queued message freezes.
- Site chat covers the conversation itself.