Summary
Downloads are unusable in OpenClaw’s isolated Chrome profile on macOS Sequoia: a generated CSV appears in chrome://downloads, but the download entry is unclickable (filename + folder icon do nothing), and the displayed filename differs from normal browsers (Neon job id, no .csv extension).
Steps to reproduce
- Run OpenClaw 2026.1.30 on macOS Sequoia 15.7.3.
- Open a tab in OpenClaw’s isolated browser profile.
- Use a web app flow that generates a CSV download (in my case: a Stocktake export flow in a Shopify admin app / Discogs Importer).
- Trigger the export so the browser attempts to download the CSV.
- Open Chrome’s built-in downloads UI: chrome://downloads.
- Click the download entry’s filename and folder icon.
Control test:
- Repeat the same export in Safari (not OpenClaw-controlled) and observe the download works and the filename is correct.
Expected behavior
The CSV should download successfully in the isolated profile, appear in chrome://downloads, and the entry should be usable:
- Clicking the filename opens the file (or starts/continues the download)
- Clicking the folder icon reveals the file in Finder
- The downloaded filename should match server intent (e.g. discogs-importer-stocktake.csv)
Actual behavior
In OpenClaw’s isolated browser profile:
- A new entry appears in chrome://downloads after generating the CSV.
- The entry is non-functional: clicking the filename does nothing; clicking the folder icon does nothing (icon visually reacts/greys).
- The filename shown in chrome://downloads is abnormal: it appears to be a Neon job number with no .csv extension.
In Safari (outside OpenClaw):
- The same export downloads successfully.
- The filename is correct: discogs-importer-stocktake.csv.
OpenClaw version
2026.1.30 (openclaw --version)
Operating system
macOS Sequoia 15.7.3
Install method
Unknown (happy to provide details if needed)
Logs, screenshots, and evidence
- Repro is visible in chrome://downloads: entry appears but is unclickable (filename + folder icon do nothing).
- Control test on Safari succeeds with correct filename.
- (Optional) Screenshot of chrome://downloads entry showing Neon job id name.
Impact and severity
Affected: anyone using OpenClaw’s isolated browser profile for web apps that require downloads (exports/reports).
Severity: High (blocks workflow).
Frequency: 100% repro for CSV in my testing.
Consequence: cannot retrieve generated CSV exports while using the isolated profile; confusing filename behavior suggests download finalization/filename resolution may be failing.
Additional information
Context: encountered while using OpenClaw during an assisted coding session (OpenClaw helping me code), but the download failure appears tied to the OpenClaw isolated browser environment since the same download works in Safari outside OpenClaw. Only CSV was tested so far.
Summary
Downloads are unusable in OpenClaw’s isolated Chrome profile on macOS Sequoia: a generated CSV appears in chrome://downloads, but the download entry is unclickable (filename + folder icon do nothing), and the displayed filename differs from normal browsers (Neon job id, no .csv extension).
Steps to reproduce
Control test:
Expected behavior
The CSV should download successfully in the isolated profile, appear in chrome://downloads, and the entry should be usable:
Actual behavior
In OpenClaw’s isolated browser profile:
In Safari (outside OpenClaw):
OpenClaw version
2026.1.30 (openclaw --version)
Operating system
macOS Sequoia 15.7.3
Install method
Unknown (happy to provide details if needed)
Logs, screenshots, and evidence
Impact and severity
Affected: anyone using OpenClaw’s isolated browser profile for web apps that require downloads (exports/reports).
Severity: High (blocks workflow).
Frequency: 100% repro for CSV in my testing.
Consequence: cannot retrieve generated CSV exports while using the isolated profile; confusing filename behavior suggests download finalization/filename resolution may be failing.
Additional information
Context: encountered while using OpenClaw during an assisted coding session (OpenClaw helping me code), but the download failure appears tied to the OpenClaw isolated browser environment since the same download works in Safari outside OpenClaw. Only CSV was tested so far.