Workflows
Attachments and context
Attachments let you inject precise context (files, diffs, text, images) into a request without pasting everything manually.
Supported attachment types
- File attachments from project paths.
- External file attachments from file picker.
- Diff attachments for targeted change review.
- Text attachments (including selected element context and skill request payloads).
- Image attachments from pasted screenshots/images.
How attachments flow into requests
- Pending attachments are captured when you send, then cleared from the session input state.
- For local runtime execution, attachments are converted into runtime attachment payloads (files/text/diffs/images).
- For remote execution, image attachments are forwarded as multimodal payloads, while non-image attachment context is materialized into prompt text.
- Large file content may be trimmed and marked so you know additional content exists.
Quality rules for better results
- Attach only files/diffs directly relevant to the current request.
- Prefer one focused diff attachment over broad unrelated file bundles.
- Use text attachments for short structured context, not full document dumps.
- Image attachments require a vision-capable model path (or auto routing).
Common pitfalls
- Attaching too many large files increases token spend and dilutes model focus.
- Binary files selected via picker are rejected for attachment.
- Duplicate attachments waste context and generally do not improve output.