Give Guide AI files and image instructions

Attachments give Codex source material for a Guide request. Attaching a file does not automatically insert it into learner-facing Guide content.

Attach supporting files

1. Open the intended Guide's Codex mode conversation.
2. Select the composer's More options plus button, then Attach files.
3. Choose the originals and wait for upload and processing.
4. Check Attached files and remove anything unintended before sending.
5. Write what the agent should read or use from each file.
6. Select Send message or Queue message.
7. Review the resulting content and any media processing status.

A prompt supports up to ten files, each containing 1–50,000,000 bytes. A nonempty message is required even when files are attached. Accepted file types, storage limits, and processing rules still apply.

Documents can provide extracted text with location references; images can provide visual input. Other formats may provide only metadata or originals, so do not assume every uploaded file was fully understood. Ask which material was used when the result depends on it.

Put an attachment into the Guide

Say explicitly when an image, audio clip, or video should become Guide content. For example: “Use the attached photograph as the first page's image.”

The agent must import suitable media and attach its resulting asset reference. Uploading conversation context alone does not accomplish this. Wait for processing and accepted Guide changes, then test the media in Preview.

Choose image sources

By default, Codex is instructed to look for Guide imagery in CodeSets. For new choice Fields, it is instructed to search for an image for each option, preserve the requested labels and values, and report missing matches.

If you prefer Pixabay, supplied images, or no images, say so in the request. Relevant CodeSet matches and external images may be unavailable; review the actual selection, wording, and source information rather than assuming every option received the right picture.

You can also change imagery manually with the Guide image browser.

Save an original to Library

Sent attachments offer Save to Library in the conversation. This creates a Library file in the attachment's associated folder. It does not add a Guide block. Wait for Saved to Library and check the folder.

Removing an attachment from an unsent prompt only removes it from that prompt's selection. It is not a delete command for existing Guide or Library content.

Recover an interrupted upload

If processing is still underway, select the same unchanged file again to check its existing upload. Successfully uploaded originals can be reused for that conversation. Changed bytes or a different filename can create a different upload.

Attachments are bound to your conversation and its folder. Moving the Guide can invalidate access to an older attachment; attach it in the current conversation context rather than repeatedly retrying the old reference. See cloud recovery.