[desktop] Chrome file upload returns "Not allowed" despite Uploads set to Always allow

Summary

Codex Desktop's Google Chrome computer-use integration cannot upload a local file even though the integration's Uploads permission is set to Always allow. The Chrome extension's Allow access to file URLs setting was already enabled before the failure.

Reproduction

1. In Codex Desktop, open Settings → Computer use → Google Chrome.
2. Confirm the extension is installed and Uploads is set to Always allow.
3. Start a Chrome computer-use task on a page with a hidden <input type="file"> and a visible associated label/button.
4. Wait for the filechooser, click the visible upload control, and call fileChooser.setFiles(...) with a valid local PDF.

Actual result

The chooser opens, but the upload fails with:

{"code":-32000,"message":"Not allowed"}
fileChooser.setFiles failed

The user reports this permission has been enabled for a long time. Restarting/reconnecting the Chrome task did not resolve it.

Expected result

With file-URL access enabled and Codex Desktop's Uploads permission set to Always allow, a user-authorized upload of a valid local PDF should complete without a permission error.

Environment

• Codex Desktop: 26.803.61601 (build 6396)
• macOS: 15.6.1
• Google Chrome: 151.0.7922.138
• Chrome integration installed
• Approval, History, Downloads, and Uploads all set to Always allow

Evidence

A screenshot was captured showing the installed Chrome integration and all four permissions set to Always allow. The issue-creation connector does not support attaching the local screenshot.

Possibly related: #21597. This report adds the permission-state evidence and a bounded Not allowed failure rather than only a hang/timeout.