Skip to main content
Data is the team-scoped file store used by platform task inputs. Upload a file once, then select it from any compatible task form without embedding the file in the task definition. Open Data to upload, download, rename, or delete files.

​
File scopes

The library lists Team shared files and My files in one searchable view. Filter by folder and file type. Team admins can also browse other members’ private folders. External collaborators can access only their own files. Team members can access their own files and team-shared files. This lets an external contributor share a task input with the internal team without exposing it to other external collaborators. Team admins can manage every file in the team. Only the uploader and team admins can rename or delete a file. A file never leaves its team.

​
Select and preview files

Click a file to toggle its selection. Drag across files or Shift-click to apply the same selection change to a range. One selected file shows a preview; selecting several shows the available batch actions. Open preview opens a shareable view, subject to the file’s access permissions.

​
Upload files

Drag files onto the page or select Upload. The browser uploads directly to platform storage and shows progress for each file. Each file must fit the upload size limit. You can select any number of files; the browser queues them and uploads up to five at a time: Zero-byte files are supported. Storage capacity scales with the team’s subscription: Pending uploads count toward storage limits until they complete or expire. The Data page shows the team’s current total against its effective storage cap. Uploads that have not completed appear as Unfinished. Delete them to free upload slots, or start another upload to refresh their status. Abandoned uploads expire after one hour.

​
Use a file in a task

When a task template exposes a supported data-file argument, its platform run form shows a file picker. The task receives the selected file reference and can stage it at a workspace-relative path when the trace starts. Use DataFileArg[DataFileRef] for one uploaded file or DataFilesArg[DataFileRef] for a list. These types enable the file picker; they do not download files into the environment. Each reference carries a file_id and an optional environment-owned destination path. The template’s setup code must request GET /v2/data/{file_id}/download with the launching member’s API key, choose a destination inside the workspace, and download the file there. Validate a supplied path before using it. Declare the staged files as data_files on the first-yield frame so the trace viewer can associate them with their platform files:
This frame describes a file already staged at inputs/report.pdf; yielding the reference does not perform the download.
hud_api_key is a reserved runtime argument. Declaring it makes hosted rollouts inject the launching member’s API key; HUD does not show or store it with the task arguments. For local runs, have the staging helper fall back to the HUD_API_KEY environment variable. The key carries that member’s HUD API permissions, so never include it in prompts, logs, traces, or grader output.
The picker lists Team shared files before My files. New uploads are team-shared by default; clear Share new uploads with team to keep one private. Private task inputs remain available only to their uploader and team admins, so other team members cannot run that task — prefer team-shared uploads. Opening an attached image, PDF, audio, text, or markdown file shows a preview; markdown is rendered in the console. The trace viewer applies the same file permissions as the Data page. Sharing a taskset, job, or trace does not grant access to an otherwise private data file. Use file tracking to inspect changes the agent makes after a file is staged into the workspace.