Save, export, and inspect output versions
Confirm file delivery, continue editing, and retain versions and sources.
On this page
Task replies and output files have separate save states. Before delivery, inspect the output list, filename, save status, and content.
Screenshots show the Chinese application interface in a Test environment with example data.
Find and save an output
- Open the file and output list in the source conversation or task.
- Open the file and confirm it matches the request.
- Save the current version to retain edits, or save as a new output for an independent copy.
- Add it to the Library for long-term reading and retrieval.
- Inspect versions and sources in file details, then reopen the saved result.
Some editable documents provide a source-and-export panel. Enter a destination within the working directory, then validate and export. Check the format and destination first.
The test task lists a generated file under Conversation files. Its name and text illustrate the location, not the result of your own exercise.
- 1Switch to the Files tab in the side panel.
- 2Choose Conversation files for files related to this conversation.
- 3Open the file marked Generated and check its actual content.
Test environment · Example data · Chinese application interface
Handle failed saving
Retry saving uses the existing output without another model call. If only a snapshot remains, try saving that content before regenerating. A write failure does not require producing a different result.
If the Agent replied with text but no file, explicitly ask for a saved file registered as a deliverable. A file existing in the working directory does not necessarily mean it is registered in the output list.
Inspect history and evidence
Use file details and history to inspect retained versions. When a source changes or becomes unavailable, the output retains information from generation time. Recheck sources before updating the conclusion.
File details and history retain saved versions. The right panel currently shows a read-only snapshot, not the editable working file.
- 1Check the saved location, version time, and source conversation.
- 2A Read-only snapshot label identifies a preserved version, not your editable file.
Test environment · Example data · Chinese application interface
Confirm delivery
Reopen the file from its destination and inspect text, media, and citations. File-integrity checks do not replace factual review or running generated code.
New-file locations in Vault and recovery: notes, general outputs, and project outputs can use different folders.
- 1Check the destination folder for each file category.
- 2Save the default locations after changing them.
Test environment · Example data · Chinese application interface
Next step
Learn to continue editing, or inspect task recovery if execution was interrupted.