Files in Agent chat

Use Attach files to select several files at once, drop files onto the composer, or paste files from your clipboard. Each file can be up to 100 MB (100,000,000 bytes), with up to 20 files per message. All file extensions and content types are accepted, including empty and extensionless files. Uploads also use your organisation's available file storage.

Wait until every file says Ready, then send your message. You can send files without text. If one upload fails, retry it or remove it before sending. Retries transfer the whole file. Keep the page open while uploading; after a refresh, completed unsent files can be recovered, while interrupted transfers may need the local file selected again. Unsent uploads expire after 24 hours.

Sent files appear on their message and can be downloaded by everyone who currently has access to that chat. People joining an app chat can access its earlier files. Removing a participant ends their access to subsequent downloads; it does not remove their sent files from retained history.

The Agent can retrieve those originals in later runs, even after its temporary workspace or cached copy is gone. Ask it to use a file from an earlier message, or identify the file by name.

New v3 Agent runs can read PDFs, PowerPoint presentations (PPT and PPTX), Word documents, spreadsheets, text files, and common images including HEIC photos. The Agent can extract slide speaker notes, calculate from spreadsheet cells, and inspect rendered pages or images when a question depends on scans, checkboxes, charts, or layout. Ask a specific question, such as “Which documents are required, and which apply only to self-employed applicants?”

Answers should identify their source file and relevant page, slide, or sheet. Small or unclear image details may need clarification. Password-protected, damaged, and unsupported formats may remain unreadable even though they can be uploaded and downloaded. Office rendering represents static pages and may substitute unavailable fonts.

Standalone chat files stay private to the chat's author until a build request converts the chat into an app conversation. That conversion keeps its history and files, which become accessible to the app's current Agent participants. File uploads require the current v3 Agent harness. Earlier runs keep their existing behavior; finish or stop an older run before answering it with files in a new message.