← Back to Channels and integrationsOpenClaw browser
Uploads, downloads, and dialogs
Browser file work is not just clicking things. It is intentionally handling upload targets, claiming downloads, and clearing prompts without losing the artifact trail.
File-flow ruleWhen the exact saved file matters, own the upload/download step explicitly instead of treating it as incidental.
Flow types
What matters in each file interaction?
UploadUse the actual file input helper and target the current input ref directly.
DownloadClaim the saved output intentionally when the resulting file is part of the deliverable.
DialogTreat the browser prompt as the real gate when the UI otherwise looks frozen.
Examples
Correct handling examples
Uploading a local assetUse the file-input-aware upload path instead of trying to type a fake path into the page.
Saving an exported reportCapture the actual downloaded file if the report is part of the promised output.
Blocked on a confirmation promptResolve the pending dialog intentionally rather than retrying clicks blindly.
Open deeper reference links for this page