Prompt queue

A coding agent's turn can run for minutes: it reads files, edits code, runs builds and checks the result. Meanwhile you think of the next thing, or spot something to fix. Without a queue you have two bad choices: wait and risk forgetting it, or interrupt and throw away work in progress. A queue adds a third. Type the message now, keep working, and the agent picks it up when the current task reaches a safe point.

Implementations differ, but they share a few behaviors. Queued messages run in the order you sent them. They can usually be taken back or edited before they run. And there's usually a way to send one immediately, which stops the current work. Claude Code, for example, queues a message you type while it's working, lists it until it's sent, lets you pull it back into the input with the up arrow, and sends queued messages right away when you press Ctrl+Enter. Agents also differ in when a queued message arrives: some deliver it between tool calls in the same turn, others only when the turn ends.

Queue additions and follow-ups: "also add a footer", "then write tests for it". Interrupt when the agent is heading somewhere wrong. A queued correction only arrives after the agent has finished doing the wrong thing. A good habit is to queue small, independent requests and keep each one self-contained, because the code may have changed by the time the agent reads it.

Queues also change how a long session feels. You can line up three or four small requests, step away, and come back to them done in order, instead of returning every few minutes to type the next one.

In a Vibely project, you can keep typing while the agent works, and each message joins a queue above the composer that runs in order. You can drag entries to reorder them, edit one (it goes back into the composer), copy it, repeat it one to three more times, remove it, pause or resume the whole queue, or clear it. Send now stops the work in progress and runs that message instead. Attachments travel with a queued message, and the queue survives a page reload. If the server is still finishing the previous run, it holds your message and Vibely retries it automatically, showing the entry as already sent. Messages Vibely itself adds are queued behind yours, so they never push your instructions back.