Prompt Queue & Attachments

You don't have to wait for an agent to finish before lining up your next prompt. Braide queues prompts when the session is busy and dispatches them in order as the agent becomes free.

When prompts queue vs dispatch immediately

A prompt dispatches immediately when the session is idle and the queue is empty.

A prompt is queued when any of these is true:

• The agent is currently running another prompt, paused, or still setting up.
• Another prompt is already waiting in the queue — fresh submissions always go to the back of the queue, never jump ahead.
• You scheduled the prompt for a future time.

Queued prompts dispatch automatically, in order, as the session becomes idle. You don't need to retry, click a "Run next" button, or refresh the view.

Attachment Lifecycle: Composing vs Submitted

Attachments (such as local media files and GitHub issues) have two distinct phases in a session:

1. Prior to Submission: When you add attachments to a prompt you are currently drafting, they appear as interactive pills in the prompt composing area (directly above the text area in the unified input shell). In this phase, they are localized to your unsent draft. You can hover to reveal the × button and detach them, or click them to preview their content.
2. Post-Submission: Once the prompt is submitted or queued, the attachments are cleared from the prompt composing area. Instead, they move to the Session Header's Attachments Button (a paperclip icon located in the toolbar next to the Reset button). Clicking this paperclip button opens the Attachments Popover, displaying all active attachments associated with the current session context.

Frozen attachment snapshots

When you queue a prompt, the attachments on the session at that moment — issues, images — are frozen onto the queued prompt. If you later detach an issue or remove an image from the session before the queued prompt runs, the queued prompt still ships with what was attached when you submitted.

This is deliberate: you submitted the prompt expecting a specific context, and that context is preserved even if you keep working on the session in the meantime.

If you want a queued prompt to run with different attachments, edit or delete it from the queue and resubmit.

Scheduled prompts

Submitting a prompt with a scheduled time holds it in the queue until that time arrives, then dispatches it. Scheduled prompts respect the same queue rules — if the session is busy when the scheduled time arrives, the prompt waits for the session to become idle before running.

See Scheduled Tasks for the full UI workflow.

Failure and retry

If a queued prompt fails to dispatch (for example, the agent failed to start at the scheduled time), it stays in the queue marked as failed with a reason. Click Retry on the failed entry to re-queue it with the same text and attachments.

If an image attachment fails to upload, any queued prompts that reference it are blocked from dispatching until the image is removed or re-uploaded — Braide will not silently ship a prompt with a missing attachment.

Multiple tabs

The queue lives on the Braide server, not in your browser tab. Two windows or tabs viewing the same session see the same queue, and changes from one are reflected in the other.