Browser Captures Go To Disk
A capture taken in the browser pane (a canvas toDataURL, a base64 image) is written to disk by a script from the tool's saved result, never transcribed by the agent into a command.
Why
A capture is proof, so it reaches the disk byte for byte.
How To Apply
- Return the base64 padded past the inline limit (a long run of spaces), so the result lands in a file. Extract it with a regex on the base64 alphabet and decode with node.
- Pixel art captures at native size, then nearest-neighbor upscaled with ffmpeg (
scale=W:H:flags=neighbor), flattened onto the app's ground color when the canvas is transparent. - Review every capture with the image reader before it lands on a page (Review Every Capture Before Reporting).
- When the project has a Playwright suite, the capture scripts there are the way (Use The E2E Pipeline For Browser Probing).
- A base64 string transcribed by hand comes out as a corrupted PNG, or as a made-up stand-in. The browser tools save a large result to a file, and a script decodes it from there without the bytes entering the context.