Summary
When attaching a local ~136MB MP4 via the native GTK “Open Files” dialog, clicking Open often does nothing: computer_use returns success, the dialog stays open, and the browser never receives the file. Drag-and-drop from the file manager also failed.
Open dismisses chooser and hands file to the page input.
Operating System
Linux
Version Information
Not available in this report; issue observed on Grok Bot computerUse / box desktop.
Additional Information
Actual
Dialog remains; file not attached. Tool result often shows success with no error. Some agents report “failed safety classification” with no quoted Auto-review error text.
Notes
Same session: YouTube Studio + Instagram eventually accepted the same file after many Open retries. Facebook, TikTok, LinkedIn, Threads never attached. In-app SendFeedback already filed; emailing [email protected] with screenshot.
Hey, thanks for the detailed report. This is a known issue with the native Open Files dialog on the Bot computer.
What’s happening: the Bot desktop has a fixed screen with a dock along the bottom edge, and the Open/Cancel buttons in the dialog often end up right on top of that dock. Your click goes to the dock instead of the button, so the dialog stays open. The file itself is fine, which is why the same MP4 eventually uploaded to YouTube Studio and Instagram when the dialog happened to be positioned higher.
Two ways to unblock yourself right now:
Ask the Bot to attach the file without using the Open dialog at all. For example: “Use your browser tool to set the page’s file input directly with the DevTools command DOM.setFileInputFiles, pointing at /home/box/Downloads/Quest_for_the_Truth_suno_square.mp4. Do not use the Open Files dialog.” This fully bypasses the dialog.
If the site still requires the dialog, ask the Bot to drag the dialog up by its title bar (or double click the title bar to maximize it) so the Open button is above the dock, then click Open.
To confirm this on your box, please send:
A screenshot of the Bot screen at the moment it clicks Open (is the Open button sitting right on top of the dock icons at the bottom, or a bit above).
The Request ID from that conversation right click the Bot message > Copy request ID.
We’re tracking the dialog geometry issue and the no dialog upload path. I’ll reply here when there’s an update.
Further evidence (2026-09-06 evening): I took over the Grok Bot computer myself. GTK Open File dialog was open on TikTok Studio upload with Quest_for_the_Truth_suno_square.mp4 selected under /home/box/Downloads/. Clicking Open as a human does nothing — the dialog stays open and the file is not handed to Chrome.
So this is not only computerUse / Auto-review. The native GTK Open button on the box appears broken for humans too.
Also escalated by email to [email protected] (same thread as the original report) with a screenshot.
@deanrie thank you — your diagnosis was right and helpful.
We tried the dock / dialog geometry fix: raising or maximizing the Open Files dialog so Open sits above the bottom dock. After that, Open worked and the local MP4 attached successfully (including on TikTok).
We also used the bypass path where we could. Attach is unblocked on our side now.
Remaining TikTok issue after attach was separate (Chrome Error 9 on Studio, then “Content check lite try again later” on Publish), not the Open dialog.
Hey, glad it worked, and thanks for coming back with the result. Raising the dialog over the doc so Open sits above the bottom bar is exactly what we need for now, until the dialog can place itself inside a clickable area.
Also really helpful that you manually checked via takeover and Open still didn’t work. That confirms this is about the GTK dialog geometry on the box, not computerUse. I shared this with the team and we’re tracking it.
On the TikTok side, Chrome Error 9 on Studio and Content check lite try again later on Publish, you’re right that’s a separate issue related to TikTok processing and moderation. It’s not related to the Open dialog. If there’s anything reproducible on the Cursor side, it’s best to start a separate thread so it’s easier to track.