# File system

**Available in:** Chats, Agents, and Projects. A Chat retains its working files alongside its conversation; Agent and Project conversations can share their owning resource’s working tree. Sites run released content rather than providing this authoring File system.

The File system holds editable work and ordinary generated outputs. It gives a Chat, Agent, or Project a place to keep files you can return to and revise as the work develops.

A durable working tree is separate from the temporary compute used to perform a task. Ending a worker does not turn its working files into disposable scratch output.

## Save and reopen a file

In a Chat, ask “Create a file named delivery-note.txt containing the words Delivery at noon.” Open **File system**, select the file, and read its contents. Reopen the same Chat to find it again.

## Work with files

Ask for a clear deliverable and identify the files that should be created or changed. For a research task, that might be a source summary, a comparison spreadsheet, and a final report. For a Project, it includes application source and supporting files.

- Use descriptive paths that make related work easy to find.
- Review changes before treating a result as final.
- Copy supplied Sources when you need independent editable content.
- Keep credentials in the supported secret or connection controls.

## Understand the owner

Conversations within a resource can work with the same tree. A file changed by another conversation is still the same working content, so coordinate simultaneous edits and review conflicts rather than assuming each conversation owns a private copy.

Historical result links identify the saved result they refer to. A later edit, move, or deletion must not be interpreted as evidence that an earlier result contained the current contents.

## Preview and retain

Supported static content can be previewed from a saved revision. A Project's application preview uses its development runtime. If preparation fails, inspect the failure and the revision being shown before assuming you are viewing the latest work.

| Goal | Destination |
| --- | --- |
| Keep editing files | File system |
| Operate a production result | [Sites](/docs/sites/overview) |
| Publish a reusable starting point | [Marketplace](/docs/marketplace/publish) |
| Retain an intentional interactive experience | [Artifacts](/docs/artifacts/overview) |

Deleting working files does not automatically delete separately retained Artifacts, template versions, or Site releases. Review each resource's lifecycle when removing work.

## Example: keep a report editable

Ask the Operator to save a report at a descriptive path, then refer to that path when requesting revisions. For example: “Update the recommendations in `research/supplier-review.md` using the new delivery constraint.”

Review the changed file and preserve the source evidence separately. If another conversation uses the same tree, coordinate edits instead of assuming it has an independent copy. See [Conversations](/docs/concepts/conversations).

## Confirm a saved deliverable

Open the named file and check its content after a revision. A response describing a change does not replace inspection of the saved result. If you intend to reuse a supplied document as working content, review [Copy to File system](/docs/services/sources#make-an-editable-copy) and the destination's access before copying it.