Attach images and files
Add screenshots, video clips, and text files to a session message.
Use attachments for evidence the agent needs to understand the task: a screenshot of a broken layout, a short recording of an interaction, or a small text file with logs or a specification.
Add and send
Open the composer's attachment menu and choose an image, video, or text-file option. You can also paste supported content into the composer. Inspect the attachment cards, wait for media uploads to finish, and send the message with an explanation of what to inspect.
Remove an unwanted attachment from its card before sending. If an upload fails, retry or remove it; a selected file is not ready until its upload completes.
Current limits
| Input | Supported formats or limit |
|---|---|
| Attachments | Up to 5 files per message, including images, videos, and text files |
| Image | PNG, JPEG, WebP; up to 10 MiB each |
| Video | MP4, WebM, QuickTime; up to 50 MiB each |
| Text files | Recognized text and source formats; up to 16,000 characters of attached text |
| Message | Typed text and inlined text files share a 20,000-character limit |
Text files are read into the message rather than uploaded as arbitrary binary files. A PDF or archive is not a text attachment simply because it contains text. Use a concise supported excerpt when the file format is rejected.
Give the evidence context
The attached clip shows the bug after I clear the search field.
The expected result is the full list. Preserve the selected category.
The text file contains the relevant client-side error.Do not include credentials or unrelated personal data in logs or screenshots. Use secrets settings when the agent needs a credential.
For a point inside a running app, preview annotations can capture the viewport context directly. To retrieve a generated file, use outputs.