Browser-agent workflows surface important resources through
result.artifacts, result.steps, status, and browser IDs. Use direct resource APIs when your application needs lower-level control.
Common recipes
Upload a file
files.path(fileId) to resolve a staged file to a runtime-local path. Prefer staged files over embedding large data directly into prompts.
Save a download
maxBytes and overwrite in production:
Handle a dialog
Grant and clear permissions
Inspect events
Download recording evidence
recording: true when the browser is created.