Skip to content

Agent Files

Give your agent files to work with — source code, data files, logs, configs, media — and store them in a place the agent can access by name. The Files tab in an agent's Knowledge area is your agent's file storage: upload files, organize them in folders, download them as needed, and optionally index files into Knowledge for full-text search.

Uploads and file storage

Your agent's Files tab shows an Uploads root directory. This is the agent's primary file storage — a flat or folder-based namespace where files are kept and accessed by path.

  • Upload files by Upload button or drag and drop them into the folder view.
  • Upload whole folders by Upload folder — the folder structure is preserved, and the agent sees the same hierarchy.
  • Files are instantly available to the agent once uploaded: the agent can read them by their path or file name (depending on the tool capabilities).

On iPhone, the grid icon next to search opens the List / Grid view menu. The upload actions stay in one row: Upload, a folder icon for Upload folder, and a download icon for Download as ZIP. Wider screens show the full button labels.

How the agent uses your files

Your agent's files are available to every run of the agent, read-only, under /tmp/agent_files/: the Uploads folders at /tmp/agent_files/uploads/<path>, mirroring what you see in the Files tab, and files the agent generated as part of its own setup at /tmp/agent_files/generated/<filename>. A run can open them by path but can't change them — that keeps what one person does from changing the agent for everyone else. Each person's own attachments and the files the agent made for them are separate: they show up at /tmp/uploads/ and /tmp/generated/ in that person's runs only. Anything the agent writes elsewhere under /tmp is automatically returned to the person as a download. See Agent learnings & agent files for what belongs to the agent and what belongs to each person.

While you are building the agent, the builder works on the agent's own files read-write: it can create folders there, ask you to upload brand assets (logos, fonts, product photos) into a specific folder, and then use those files — for example, to place them into the agent's frontend. In the builder's workspace the agent's files sit at /tmp/uploads/ (the agent's own runs see the same files, read-only, at /tmp/agent_files/uploads/). Whatever the builder creates or changes there appears in the Files tab right after the run, within the same storage limits as your own uploads.

Files you attach in chat

Files and images you attach to a chat message are saved to your own files on that agent, inside a folder named after the conversation — the first 8 characters of its id, for example 8bce66d3/. Only you see them; they are not added to the agent's Files tab. The agent sees that folder at /tmp/uploads/8bce66d3/, and it stays available for the rest of the conversation: in a later message you can say "use the photo I sent earlier" and the agent opens it — or uses it as the reference for a new image or video — without you attaching it again.

  • Pasted images have no file name of their own, so they are saved with a generated one such as image-1a2b3c4d.png.
  • Attaching a second file with the same name in the same conversation keeps both: the new one is saved as report (2).pdf.
  • Files the owner uploads in the agent's Files tab are agent files, shared with every run, and stay in the folder they chose.
  • The Files view shows such a folder under the conversation's title, with the short id beside it; the folder itself keeps the short id. In the chat with your main assistant, the same Files view opens from the chat header — see Chat & your main assistant.

Workflow run files

A workflow run acts as the person who triggered it — whoever set up the schedule or webhook that started it; the person who pressed Run, for a manual run (see Whose run it is). Like a chat run, it reads the agent's own files read-only at /tmp/agent_files/ and writes into that person's own files on the agent, never into the agent's Files tab. A file one run produces is there for that person's next run and for their chats with the agent, and nobody else sees it. That's the ordinary case, because a workflow's webhook trigger ships with Max parallel runs off (its default is 1): only one run of a workflow executes at a time for each person.

Raise Max parallel runs above 1 and every webhook delivery of that workflow gets its own private folder inside those files instead — as soon as the pool itself is raised, not only once two deliveries actually overlap — so two deliveries genuinely in flight at once can't overwrite each other's working files. Those folders are named with internal identifiers rather than the workflow's name or the run's date, so you can't yet tell which run a folder belongs to just by looking at it. The files inside are exactly what that run produced, and they do not carry over to the next run.

File limits and replacement

Each agent has storage limits:

  • Per-file limit: 100 MB per file.
  • Per-agent quota: 2 GB of total storage by default (configurable by an administrator).

If you upload a file with the same path as an existing file, a Replace dialog appears:

  • Replace — the existing file is overwritten with the new version.
  • Skip — the new file is not uploaded, and the existing file is kept unchanged.

This makes re-uploading a file or re-running a batch upload safe: you won't accidentally duplicate files or lose changes.

Knowledge indexing

By default, uploaded files are stored but not indexed for full-text search. You can additionally index a file so its content becomes searchable:

  • Add to Knowledge — index a supported file type (see Documents & RAG for the full list) so the agent can search its content. This is shown as a + button in the file row or in the row menu.
  • Once indexed, the file appears in the agent's Knowledge and contributes passages to the agent's search results when it answers questions.
  • Remove from Knowledge — stop indexing the file without deleting it. The file remains in the Files tab, but is no longer searchable. Remove from Knowledge if you want to keep a file available but don't want it included in the agent's search index (for example, a reference file that clutters results but shouldn't be deleted).

Indexing is optional: a file in the Files tab works for the agent to read directly, and doesn't require indexing.

Opening files

Click a file to open it. Images open in a full-screen viewer — use the arrow keys or the on-screen arrows to flip through the other images in the folder, or swipe sideways on a phone or tablet, and press Esc to close it. The download icon in the corner saves an agent file; to save an image from your own files, use Download in its row.

Other files open in a preview over the Files view; on a phone the preview fills the screen. It uses the canvas's viewers: an HTML page runs, a PDF shows where the browser can display one, video and audio play, and a CSV, Markdown, code or plain-text file shows as a table or as text. Above the file, Open in new tab shows it in a browser tab of its own and Download saves it. A file the preview can't show — a Word or PowerPoint document, an archive, an Excel workbook — appears as a card with its name and Download.

Folder What the preview shows
Workspace Every type in the list above. A slide deck or a page wider than the preview is scaled down the same way as on the canvas
Generated Every type in the list above. A page keeps the width it was laid out for, so a wide slide deck scrolls sideways
Uploads Images, video, audio and PDFs. Other files, text included, appear as the card

In the Android, iPhone, iPad and Mac apps, a file opens inside the app, in the same viewers as the canvas. An HTML page opened from Files keeps the width it was laid out for, so a wide slide deck scrolls sideways; on the canvas the same deck is scaled down to the screen. A file the app can't show opens as a card with Download, Share and Open in another app. An Excel workbook (.xlsx) opened from Files shows that card on Android and opens in the system preview on iPhone, iPad and Mac.

Downloading files

You can download files to your computer:

  • Download a single file from the file row or the preview. A file in the agent's workspace or one it generated is saved straight to your computer; an uploaded file opens in a new browser tab, where you can save it.
  • Download as ZIP for a folder or the entire Uploads root — all files and subfolders are packaged into a ZIP archive.

The ZIP download includes the folder structure so you can extract it and see the same layout locally.

In the Android and Mac apps, a downloaded file or ZIP archive goes to Downloads. On iPhone and iPad, the app asks where to save it.

Deleting files

Delete files or folders from the Files tab:

  • Deleting a file removes it from storage and from the agent's access.
  • Deleting a folder removes all files and subfolders inside it.
  • If any files in the folder (or subfolders) were indexed into Knowledge, their indexed data is also removed — they no longer contribute to the agent's search.

Deletion is permanent and cannot be undone, so take care when removing files or folders.