Browser Use blocks a local file URL despite “Always allow” approval settings

What version of the Codex App are you using (From “About Codex” dialog)?

26.901.20858 (from desktop app logs)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

The desktop app's Browser Use tool refuses to open an existing local HTML report via a file:// URL. The same report can be opened manually in the built-in browser.

Error:
“Browser Use rejected this action due to browser security policy. Reason: The browser URL policy blocks this action.”

Current settings:

• Built-in browser control is enabled.
• Website approval is set to “Always allow”.
• No site-specific permission overrides are configured.
• Full CDP access is enabled.

Restarting the desktop app did not resolve the issue. App logs show browser_use available=true and cua_repl status=ready.

The exact blocking rule is unknown. Please clarify whether this is an intended restriction or a bug, and how access can be restored through supported settings.

What steps can reproduce the bug?

Observed steps in the affected session:

1. Open an existing local HTML report manually in the built-in browser.
2. Ask the agent to open the same file:// URL and inspect the rendered report.
3. The Browser Use tool rejects the request with the URL policy error.
4. Confirm the browser settings above and restart the app.
5. Retry the same URL; the rejection persists.

The report and its full path are omitted because they contain private business information. Reproduction with a separate minimal HTML file has not been tested.

What is the expected behavior?

The agent should either access the explicitly authorized local report, or provide a specific explanation of the blocking rule and a supported recovery path.

Additional information

Feedback was successfully uploaded from the desktop app.

Feedback/session ID:
019fa863-d610-73b1-87c5-c0c93acb84fe

Start by reproducing the Browser Use request with a minimal local HTML file, since the reported business report and full path are private and minimal reproduction has not been tested. Inspect the browser URL policy handling and app logs for the file:// rejection; done means either authorized local reports open successfully or the blocking rule and supported recovery path are documented.