Sending a message gives the Operator a request to work on. You can then follow its progress, stop the current work, or prepare another message. The available controls depend on whether work is running and whether a previous message can still be revised.
Send a message
Review your text, selected mentions, and attachments, then use the send control. A message can contain text, attachments, or both. Attachments must finish uploading first.
A submitted message belongs to a conversation. The work it starts has its own lifecycle, so a saved message and a completed result are different things.
Stop current work
Use Stop to request that the active work stop. When work is running and the draft is empty, the main Composer control offers Stop. A new draft makes the send control available for the selected delivery behavior.
Stopping work does not undo actions already completed. Review the conversation and any resulting changes before deciding what to do next.
Edit and resend
When a message offers Edit and resend, open it to bring its text, attachments, and references back into the Composer. Make the correction, then use Save and rerun. Cancel editing to return to the draft you were preparing before the edit.
Use this when the request itself needs a correction—for example, changing the audience or supplying a missing constraint. The action is available only when the selected turn can be replaced.
Where Retry is available, it also brings the previous request into the editing flow. Review it before running again. A rerun can produce a different result and perform additional work; it does not reverse earlier external actions.
Queue or steer
The delivery control determines what happens to a new message while work is already running.
| Mode | Behavior | Use case |
|---|---|---|
| Decline while busy | Keeps the new message in the Composer until the current run finishes | You want to review the result before submitting more work |
| Queue messages | Holds messages until the current run finishes, then processes them in order | You have a follow-up task that can wait |
| Steer current work | Sends guidance into the active run | You want to redirect the work in progress |
For example, queue “After the draft, prepare a short summary” as a follow-up. Steer with “Focus on customer benefits; leave out internal implementation details” when that should shape the current work.
Steering is guidance to the active work, not an undo action. Queued messages can require an explicit continuation when the run is held; use the conversation's continuation control when it is offered.
Recall a previous prompt
From an empty Composer, use the up arrow to recall your previous prompt text. Review it before submitting. Prompt history recalls text rather than restoring the original attachments and resource references; add those explicitly when they are needed again.
Example: correct the input during analysis
You notice that a report being analyzed contains last month's figures. If the correction should affect the active task, attach the correct report and steer with: “Use this report instead of the earlier attachment; compare the same periods.” If the first analysis should finish before a separate comparison, queue that comparison instead.
Review the resulting dates and figures against the new Source. A steering message does not erase files already written or actions already completed.