Files and results

Attach source material to a request and ask the Bot to return work in a form you can inspect, edit, and hand off.

Use the attachment control or drag files into the composer. You can also paste images and links.

Common supported inputs include:

• images, audio, and video;
• PDF and plain-text documents;
• Word, Excel, and PowerPoint files;
• CSV, JSON, YAML, and source-code files;
• HTML and email files; and
• Jupyter notebooks.

The desktop composer accepts up to six attachments at a time. Documents, images, and audio can be up to 25 MB each; videos can be up to 200 MB. Large, encrypted, damaged, or unusual files may not be readable.

Tell the Bot what each attachment is and how it should use it:

The PDF is the signed policy. The spreadsheet is this month's transactions. Reconcile the spreadsheet against the policy, cite the relevant policy section for every exception, and return a new spreadsheet plus a short summary. Do not modify the originals.

Paste a link when the Bot can access the page from its computer or a connector. If the page is private, sign in through the computer or install the relevant connector.

Links in messages and results open in an in-app viewer when possible. Always check the destination before entering credentials or approving an external action.

Specify the artifact and its acceptance criteria:

• a document with headings and source links;
• a spreadsheet with defined columns and formulas;
• a slide deck with speaker notes;
• a folder containing screenshots and logs;
• a draft message that has not been sent; or
• a short recommendation followed by the underlying evidence.

For consequential work, ask the Bot to separate:

1. facts found in source systems;
2. assumptions or inferences;
3. actions already completed;
4. actions waiting for approval; and
5. unresolved questions.

Files, images, links, and tool results appear as cards in the conversation. Open a card to preview supported formats. You can then save the file, open the source link, or continue the conversation with feedback.

Ask the Bot to revise the existing artifact instead of making disconnected copies:

Update the report you just created. Add source links to the first two claims and replace the final table with a CSV attachment.

A strong result should be independently reviewable. Depending on the task, ask for:

• direct source links;
• screenshots with the relevant state visible;
• timestamps and time zones;
• input and output file names;
• a concise action log; and
• an explicit list of anything the Bot could not verify.

Do not rely on a screenshot alone for rapidly changing data. Keep a link or export from the source system when possible.

Bots can read files other Bots save in /workspace. Use project folders and descriptive names to make handoffs reliable.

The shared workspace is useful for intermediate material, but the conversation should still contain the final result or a clear link to it. See Use the computer and apps for persistence and recovery details.