The composer sends to the currently selected conversation. Before submitting, verify the project, session title, and any recipient mention. A useful request describes an outcome, a scope, and how completion should be checked.
#Send a request
- Select the intended session.
- Type your request.
- Add any required files or context.
- Review attachment and mention chips.
- Use Send, or press Enter on a desktop keyboard.
- Watch the transcript, queue, and execution status.
On touch devices, Enter inserts a newline; use the Send button. Shift+Enter adds a newline on desktop. Ctrl+J also inserts a newline in the composer.
For example: “Fix the empty-state message in the search panel. Change only the existing component and styles. Run the relevant check and show the diff. Do not commit.”
Give corrections as concrete instructions. If work is already running, another message can enter the queue; submission does not necessarily interrupt the current tool action.
#Read the controls
While processing, the composer can display Send when you have content and Stop when it is empty. Use Stop deliberately when you need execution interrupted. Review suggested text before sending it.
A question or approval card may need an answer before work can continue. Respond to that card rather than typing unrelated text and assuming it answers the pending request.
#Revise before delivery
An unsent draft is different from a queued message. Edit your draft directly. For a queued message, use its own edit controls and save the change. Once delivery starts, cancellation or editing may no longer have the same effect.
Attachments, pasted blocks, mentions, and schedule delay are part of the outgoing request. Remove outdated context when changing tasks; deleting visible prose alone may leave a chip attached.
Use Attachments and context, Mentions, voice, and slash commands, and Delayed messages for those controls. For an interrupted or uncertain delivery, see Stop and recovery.