Attach files, images, and links to a request
Give an agent the evidence it needs alongside the request.
Last updated 16 September 2026
Give an agent the evidence it needs alongside the request.
Before you start
Select the destination project before attaching an image. Use only the files and references needed for this task.
The file and document chips identify the attached context. The request also states what to inspect and explicitly keeps this example read-only; it has not been sent.
Step by step
In the composer, type @ to select files or folders, or @@ to select a project doc. Use the picker rather than relying on an ambiguous filename.
Attach or paste an image and wait for attachment processing to finish.
For a URL, include it in the brief and explain which part is relevant. Mention whether a screenshot is a visual reference or a bug example.
Review the context and message together, then send. For example: “Use this screenshot for spacing and hierarchy; keep our current text and colors.”
What to expect
The sent request contains the context and instructions needed to interpret it.
Troubleshooting and useful details
If sending is blocked while an image attaches, wait for completion or resolve the attachment error. A reference alone does not explain what should change; add an explicit outcome.