Attachments
Add images, screenshots, diagrams, and reference files when visual or structured context will improve the task.
When to attach a file
Attachments are useful for bug reports, UI changes, design references, logs, diagrams, and project files that are easier to inspect visually than to describe in text.
- Use screenshots for visual defects
- Attach logs for reproducible failures
- Include reference images for layout work
- Keep sensitive data out of attachments
Model support
Visual inputs are processed only when the selected model and provider support multimodal input. If a model does not support an attachment, describe the important details in text or use a provider that supports them.
Describe the intent
An attachment works best with a short instruction: what to inspect, what should change, and how to verify the result.
Review before sharing
Check attachments for credentials, private information, customer data, and unrelated project context before sending them to a provider or including them in a session.