Skip to main content

Send messages

Add task context, queue follow-up messages, and steer work during execution.

Add files and relevant capabilities when composing a task. You can also send messages while it runs: steer to change its current direction, or queue a request for later.

Choose capabilities and context

While composing a message, select a capability, mention an Agent, or reference material directly from the composer:
Entry pointPurposeExample items
Type /Select a capability, invoke a Command, or mention an AgentSkills, plugins, MCP connectors, Commands, and Agents
Type @Mention an Agent or reference contextAgents, existing task or conversation records, documents, workspace files, or folders, connected browser tabs
Add attachmentSupply materials such as imagesAttachments to analyze in this request
After typing / or @, use the Up and Down arrow keys to choose an item, then press Enter or Tab to add it. Press Esc to close the list. You can also open Add context to browse available items. The candidates depend on the current workspace, installed and enabled capabilities, and accessible materials. In the slash menu, use Left and Right to switch between recent items, modes, Skills, plugins, connectors, commands, and Agents. Choose items to match the task:
  • Reuse recurring requirements: select a Command with /, then specify what to work on this time. Save a recurring handoff format or review workflow as a custom command.
  • Combine context with a Skill: when reviewing a design, use @ to reference the design document and / to select a relevant review Skill, then describe the compatibility risks to check.
Add a clear goal, scope, and expected output to make the request easier to follow. After selecting Sites or the PPT plugin capability, you can also send a ready template or reference attachment without adding text. A capability chip alone cannot submit an empty task. Use App snapshots to add the foreground window as context. See Voice input and Context management for related workflows. Type @ in the composer, select a tab from a connected, supported browser, add your request, and send. Available tabs and readable content depend on the browser connection, authorization, and execution environment. See Built-in browser for details.

Reuse input and context

  • Find files: Enter part of a file or folder name after @. Suggestions respect the workspace’s Git ignore rules.
  • Reuse materials: Retrieve text from input history, or use available image-preview actions to copy, save, or add an image to the task. Check the goal and attachments before sending.
  • Reference another device: After connecting the device and authorizing its workspace, use @ to delegate work to that workspace or reference cached conversations. The current task stays local. Offline devices provide cached content only, which may be outdated and still requires valid identity and authorization.
In a connected-device conversation, use the / menu to create an automation. That device manages its schedule and records.

Accept a next-step suggestion

When the composer is idle and empty, a text suggestion may appear. Press Tab or Right Arrow to insert it into the draft, then edit it and send when ready. Accepting a suggestion does not start a task.

Queue and steer messages

MethodUse caseBehavior
QueueHandle another request after the current workKeeps the message in the pending queue.
SteerCorrect the direction or add constraintsDelivers input at a safe execution boundary without directly stopping the current run.
Choose the default under Settings → General → Input while running. When steering is supported, use ⌘+Enter on macOS or Ctrl+Enter on Windows. Steering is not necessarily immediate. Check composer hints when the environment does not support it, context is being compacted, or requests are pending. Use the stop button to stop execution.

Manage queued messages

Queued messages appear above the composer. Choose Steer, or Move back to the composer to edit to return the text to the composer and resend it after changes. Use Remove when it is no longer needed. With multiple queued messages, you can change their order. For example, queue “write usage instructions afterward,” and steer with “limit the remaining work to sign-in” when the current scope needs correction. Make each request explicit to avoid repeating external operations.