Attachments, Models, and Skills

Add reference images or supported documents and choose the Runner capabilities that fit a request.

What this covers: You will give Runner the right context and working tools before sending a request.

Images show Runner what you mean. Models and skills change the capabilities available for the next request. When Attach appears, you can also give Runner supported documents as context. Use them deliberately; a clear request is still the most important input.

Entry path: Open a store project → conversation composer.

Before you start

• Use only images you are allowed to share with the current workspace.
• Remove secrets, payment data, and unnecessary customer information.
• Check plan and browser access when a model, Skill, or screen-capture action is missing.

Composer controls

In the image-only picker, Runner ignores an image with the same name and size as one already in the draft and shows Duplicate image ignored. Unsupported files are ignored with Use a JPG, PNG, GIF, WebP, BMP, or TIFF image. In a mixed selection, supported images remain available. Runner accepts up to 10 attachments per message. Images can be up to 32 MB each. When document attachments are enabled, documents can be up to 10 MB each.

English callouts highlight the controls. Select the image to enlarge it.

This workspace has document attachments enabled, so the menu shows Attach. Opening the menu does not upload a file or send the request.

Add an image

1. Draft enough of the request to explain why the file matters.
2. Select Add on desktop, or the upload button on mobile.
3. Choose Upload image, Picture, or Take screenshot, depending on what is shown.
4. Pick or capture the relevant image.
5. Confirm that the correct image thumbnail appears with the draft and that any upload progress has finished.
6. Remove it before sending if it is the wrong reference.
7. Select Send message.

If screen capture is unavailable or permission is denied, take a screenshot with your device and upload the saved image instead.

Attach a document when available

1. Open Add and select Attach. If only Upload image or Picture appears, this workspace does not support documents in this composer.
2. Choose a supported file, such as a PDF, Word document, presentation, spreadsheet, or CSV.
3. Confirm the attachment appears beside your draft.
4. Tell Runner what to use from it, for example “Use the product names and descriptions in this CSV to draft collection copy; do not change prices.”
5. Select Send message and wait for document preparation to finish.
6. Check that Runner’s answer reflects the intended document before asking for a store change.

If the file cannot be read, follow the displayed error. Password-protected, damaged, overly complex, or empty documents can fail. Use an unlocked, smaller export or paste the relevant text; keep your draft until the replacement is accepted. Videos are not supported by this attachment flow.

Choose a model

1. Select the current model in the composer.
2. Review the models Runner makes available. The recorded interface shows Runner 2.0 Pro; use the label in your own selector because available profiles can change.
3. Choose the model that matches the task.
4. Confirm the selected model is shown before you send.

If a model is locked, keep the current model or follow the plan information Runner opens. A locked choice is not applied to the draft.

Add a skill

1. Open the composer’s Quick commands or Skills control when shown.
2. Search or browse for the capability you need.
3. Select an available skill for this request. Quick commands can place its slash command in the composer, such as /store-seo; selecting it does not execute the command.
4. Return to the composer and confirm the intended skill or slash command is present. Add the task-specific instructions before sending.
5. Send the request.

The separate Agent command palette manages capability state: choosing a row can install, activate, or pause a Skill. It is not the same as selecting a Skill in the composer.

When the current plan does not include a skill, Runner can open the Agent or upgrade path instead. Memory choices appear only when memory is enabled for the account.

Selecting a command prepares the draft. Add your request and review it before sending.

Watch: prepare a quick command

The recording selects store-seo into the composer and leaves it unsent. No SEO analysis starts.

Troubleshooting

Related guides

• Write effective requests
• Agent command palette
• Chat with Runner
• Workspace settings