Skip to main content
Files holds everything attached to your project, split by whether you put it there or the platform did.
The Files panel showing tabs for All, User Uploaded and System Generated, a search field, an Upload Files button, a total count, type filter chips for Word, Excel, PowerPoint, PDF, Images and Others, and a file list with User and System badges.

The Files panel. Tabs split the list by origin; the badge on each row repeats it.

Two Kinds of File

System files cannot be deleted from this panel. They are outputs of something else, so removing them here would leave the thing that produced them out of step. Each row carries a badge repeating its category, so the distinction is visible in the combined All view too.

Adding Files

Upload Files adds to the project. You can also attach files directly to a prompt with the paperclip in the composer, and those attachments land here too. Uploads accept images and documents: Images are capped at 2 MB. Filenames are capped at 200 characters.

Finding Things

Search by name, or narrow by type using the chips: Word, Excel, PowerPoint, PDF, Images, and Others. The list sorts by name, date modified, or type, and a count above it reports the total.

Why This Panel Matters

Files are how work moves between modes. Build Mode does not inherit your Prototype conversation, so anything that should influence a build has to be attached to a prompt, and this is where you find it again. See Output Handoff. It is also where generated documents accumulate. A blueprint written in the CAB workspace appears here as CAB.md, available to attach to a build prompt like any other file.

Your Next Step

Files feed prompts. What the agent does with them is the next thing worth knowing.

Attach files to a build

How context reaches the agent.

Carry prototype work forward

Saving output so it survives the switch to Build.