Show the agent what you mean

3 minute read · Chats & Local Agents

A screenshot or sketch can explain a design change better than a paragraph. Attach it to the draft or conversation, then say which part the agent should use.

• Add useful context
• Create an image where supported
• Attach only what the task needs
• Work with generated images
• Export and troubleshoot

Add useful context#

Select supported files or images with the attachment controls. Preview them in the gallery before sending. Include only material you intend the chosen provider to see. A reference image guides a request; it does not give an agent permission to read unrelated folders.

You can inspect and export supported attachments through the project tools. Saved content uses encrypted storage, and cleanup should keep an attachment while another conversation still references it.

Create an image where supported#

Codex’s built-in image generation uses your connected Codex account when available. Generated images appear in the conversation and can be exported into the selected project. Other providers do not gain the same capability simply because an image tool exists.

An optional, separately billed image API connection is a different path and needs explicit selection. If the provider cannot generate the image, read its actual availability error rather than assuming you need to upgrade Vortex.

See conversation context and provider usage.

Attach only what the task needs#

Add a supported file or image from the composer, inspect its preview and explain how the agent should use it. A sketch can guide layout; a screenshot can demonstrate a bug; a small sample file can define an import format. Remove accidental attachments before sending, especially files with credentials or customer data.

Attachments are associated with the account, draft/conversation and project context. Their name, MIME type and size help identify them; content is stored through the encrypted attachment path. A file that remains referenced by another conversation must not disappear merely because one chat is deleted.

Work with generated images#

When Codex exposes built-in image generation for the connected account, ask for the intended scene, style and use. Inspect the generated image in the conversation before exporting it into the chosen project. Ask for a revision with the changes you want rather than silently substituting an unrelated stock image.

A separately billed image API connection is an optional, distinct path. It requires explicit selection and authorization. A missing key for that optional path does not imply that a provider's built-in image capability is unavailable. Other providers do not automatically gain image generation simply because the Vortex image tool exists.

Export and troubleshoot#

Choose the target project and filename deliberately when exporting. Opening an image in the gallery is not the same as adding it to the app's assets or referencing it from a page. Ask the agent to wire the exported file into the UI, then reload Preview and inspect the result.

If an attachment will not open, check its format, size, account scope and Vault state. Preserve the original file while diagnosing a missing encrypted copy. When reporting the failure, include the type and size rather than uploading private content unnecessarily. See file review.