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. Click files to select them. Drag across files, or Shift-click, to repeat the last check or uncheck for every file in that span. With more than one selected, the right pane lists the selection and the delete action that applies.

​
File scopes

The library lists Team shared files and My files in one searchable view, with a preview of the highlighted file. Click a file to add it to the selection; click again to remove it. Drag across files, or Shift-click, to repeat that check or uncheck across the span. Two or more selected files replace the preview with the selection and its actions. Filter by where a file lives and by type. Team admins also see other members’ private folders. Open preview writes ?preview=<file id> so that view can be shared; the preview panel can copy that link or rename the file. 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.

​
Upload files

Drag files onto the page or select Upload. The browser uploads directly to platform storage and shows progress for each file. The transfer path limits each object and bounds parallel work; these limits do not cap how many files you may select or store: You can select any number of files, including zero-byte files. The browser queues the selection and transfers at most five files concurrently. 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. Unfinished uploads (reserved but never completed) show as Unfinished in Data; delete them to free the five-at-a-time in-progress cap. Starting a new upload also publishes or drops abandoned reservations automatically. A sweeper drops reservations older than one hour (the PUT URL lifetime).

​
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. Declare one uploaded file with DataFileArg[DataFileRef], or many with DataFilesArg[DataFileRef]:
The SDK publishes the argument hint in the template schema, so the platform renders the upload picker and stores each selection as {file_id, path}. At task start, attachments arrives as list[DataFileRef]. The hint does not copy bytes into the environment. In the example, stage_data_files is an environment-owned helper that calls GET /v2/data/{file_id}/download, writes the returned file under /workspace, and returns the staged {file_id, path} entries.
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.
Returning the staged entries as data_files on the first-yield frame lets the trace viewer associate the workspace paths with their platform files. PromptArg and GradingArg[T] use the same hint mechanism for prompt and grading editors; ordinary typed parameters use the standard schema form. The picker lists Team shared files before My files. Click to toggle files; drag or Shift-click repeats that check or uncheck across the files in between, same as on the Data page. 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.