Upload files and review results¶
Conversation attachments are suitable for a current task. Add information that should remain available across conversations to a knowledge base.
Add files¶
In the input area, open + and choose the file-upload action, or drag files into the input area. You can also use the attachment-pasting method supported by the page.
Check attachment names and remove any incorrect files.
State whether you want a summary, comparison, extraction, or calculation.
Wait for attachments to be ready, then send the message. Follow the upload prompt for current file-format and size limits.
For multiple files, explain their relationship. For example: “Use the product specification as the main source and apply updates from the change email.” This helps distinguish materials from different dates.
Review the originals¶
Select the attachment count in the conversation to open the file panel on the right. Select a file to preview it. The panel provides download, expanded-preview, and close controls; adjust its width when you need to read it alongside the answer.
Uploaded files are inputs. A generated-file result is available only when the answer contains a file or download entry and you can open the resulting file. Report text alone is not a report file.
Use answer actions¶
Actions near an answer include copying, quoting, exporting, and positive or negative feedback. Copy to reuse text, or quote a passage to ask a focused follow-up question. For export, follow the options in the dialog and inspect the result. Supported formats depend on the content and available interface options.
Troubleshoot file results¶
Problem |
What to do |
|---|---|
An attachment was omitted |
Check the sent attachment list and name the missing file in a follow-up |
An image or scan is unclear |
Inspect its preview and provide readable text or a clearer file |
The answer lacks evidence |
Ask for file names and supporting passages, then verify each item |
A generated file is missing |
Check for an actual file entry; if only text was produced, explicitly request a file and check again |