Files

There are two separate file scopes:

Files	Who controls them	What they are for
Room source files	Room owner	Protected data used in the room's analysis
Your supporting files	Your account	Briefs, examples, code, and documents you choose for a request

Room source files

As an owner, open a room's Files card to add, replace, or remove a file. A successful write means the file is ready for future runs. A failed replacement keeps the previous file. Members cannot download the owner's source files.

Supporting files

Choose only the personal files relevant to your analysis request. Files remain private to your account until you select them for a run; selecting a file supplies that version to the room's evaluator. The owner's question review includes the file's name, size, and checksum, not a download of its contents. Do not attach a document you are unwilling to share for that review.

Paths look like /research/brief.md. Folders are derived from file paths; there is no separate folder creation step. Paths are case-sensitive. Traversal (..), backslashes, control characters, and empty path segments are rejected.

Personal files must be nonempty, pass scanning, and be at most 25 MiB each. A run can select at most 20 files, totaling 100 MiB. Uploading a document does not mean its full text is automatically inserted into the model prompt.

Frozen inputs

Starting a run freezes both the selected supporting-file versions and the room source snapshot. Replacing or deleting a file later affects future runs; it does not change the inputs of a run already started.

The evaluator receives selected supporting files read-only under /inputs, preserving their paths. Unselected personal files are absent. Protected room source data remains separate.

For file operations and exact limits, see the agent guide.