Upload Reference
Supported onboarding and workspace file rules.
Onboarding Sources
| Rule | Value |
|---|---|
| Extensions | .md, .markdown, .txt, .csv, .json, .yaml, .yml, .toml, .pdf |
| Maximum source size | 50 MB |
| Maximum filename length | 240 characters |
| Text encoding | UTF-8 |
| PDF requirement | Readable text layer |
| Required scopes | Organization and every selected department |
Original PDFs are retained and searchable Markdown is derived from their text. Image-only scans are not currently an accepted evidence source.
Workspace Files
Agent workspaces reject absolute paths, traversal outside the workspace, unsafe relative paths, and unsupported local file types. Declared output directories determine which artifacts can be synchronized. A task run may create or change at most 100 files beneath those output directories. The runtime checks the complete candidate set before uploading, so an over-limit run writes no objects and fails with a repairable file-limit error. Temporary files outside declared outputs do not count, but they are never synchronized. Chat workspaces keep their separate continuity model.
Integration CLI Files
Trusted CLI uploads and downloads must remain inside the active run workspace. The current Google Workspace gateway caps one invocation at 50 MB and uses temporary restricted-permission files.
File Upload Questions
Structured onboarding questions may request files with a narrower accepted-type list and size limit. The question contract wins when it is more restrictive than the general onboarding list.