Use files and retrieve your work
Attach the specific material your task needs, wait for it to become usable, and check the result against that material. A file appearing in the interface does not establish that its entire contents were read correctly.
On this page
These controls describe the October 2026 development interface; file controls, formats and limits may differ in your installed release.
Add a file from your computer
- Open the session that will receive the task.
- Use the composer's Upload file or image control and choose Local file.
- Select a small, non-sensitive file. Start with plain text when possible.
- Check the attachment's name and any upload or processing status before sending.
- Write what the agent should do with that file, the required output and any restrictions. Then choose Send message.
For example: “Read the attached project notes. Return three action items with the owner and due date stated in the file. Mark missing fields as unknown. Do not modify the source or send the result elsewhere.” Use this as a prompt template and check your actual result.
The composer allows up to four attachments. The server supplies allowed file types and individual size limits; a file-picker extension filter is not a promise that every file of that extension will be accepted or fully understood.
Use a file already in the workspace
Choose Workspace file from the same menu. In Select workspace file, navigate to the intended file and open it with a double-click. Check that the intended attachment appears before sending your request.
Workspace paths belong to the AgReady instance. Typing a path from your laptop into a remote session does not upload the file or grant the server access to that laptop. Use the local-file picker to provide a file from the browser's machine.
The workspace browser shows the areas available to your account. Session files and uploaded files are different groups: uploads belong to the user's upload area, while generated session outputs can appear under that session's artifacts. Shared areas depend on access permissions. Visibility in the browser does not imply that every tool has permission to modify the file.
Wait for processing—and check coverage
Some files need processing before submission. Pending, processing, failed and too-large states block sending in this interface. Read the displayed error rather than repeatedly attaching the same file.
A partial result needs special care: it must not be treated as evidence that the whole document was read. Ask the task to identify unavailable sections and avoid conclusions that depend on missing content. For a critical passage, provide a small readable excerpt explicitly.
For a rejected file, use an allowed format or a smaller relevant extract. Do not rename an unsupported extension to disguise the file type. Remove secrets and unrelated material before uploading. Content used in model requests may be sent to the configured provider.
Find and retrieve an output
- First distinguish a response in the conversation from an actual saved file. The introductory text-only task produces a response, not an output file.
- If your task calls for a file and the run reports creating one, open Session files for that session.
- Refresh the file list if needed and inspect the relevant artifact. An empty new session directory is not itself an error; a file may not have been created yet.
- Open an available preview or use the file's download control. Preview availability depends on the file type and service support.
- Check the downloaded file's content and format. A path in a message is not, by itself, proof of a complete deliverable.
If a preview fails, distinguish that failure from a missing file. If the file is absent, check the requested output, task result and any tool error before retrying. Do not broaden permissions merely because a file operation failed.
Preserve originals and scope
For edits, request a separate output and name it clearly instead of casually overwriting the source. File visibility does not authorize deletion, publication or sharing. Do not assume that clearing a conversation securely deletes uploaded or generated files; retention and deletion require separate, verified procedures.