codex - 💡(How to fix) Fix Browser Use blocks external and custom-host URLs with "cannot determine if ... is allowed" on macOS app [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19270Fetched 2026-04-24 10:39:40
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Error Message

In the Codex macOS desktop app, Browser Use can control the in-app browser for explicit local URLs such as 127.0.0.1 and localhost, but it blocks public external URLs with an allow/preflight error. The error is: It fails with this allow/preflight style error: 2. surface a clearer permission prompt/error explaining which allow/preflight check failed. That issue reports a different low-level error on Windows, but it also points to Browser Use external navigation and site_status / allow preflight behavior.

Code Example

Browser Use cannot determine if https://www.google.com is allowed. Please try again later or use another source.

---

Browser Use cannot determine if https://www.google.com is allowed. Please try again later or use another source.
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

In the Codex macOS desktop app, Browser Use can control the in-app browser for explicit local URLs such as 127.0.0.1 and localhost, but it blocks public external URLs with an allow/preflight error.

The error is:

Browser Use cannot determine if https://www.google.com is allowed. Please try again later or use another source.

Environment

  • OS: macOS 15.7.4
  • Codex Desktop originator: Codex Desktop
  • Browser Use plugin: openai-bundled/browser-use/0.1.0-alpha1
  • In-app browser backend: iab
  • Explicit local development URLs such as http://127.0.0.1:<port>/... work.

What works

Browser Use can open and inspect explicit local URLs:

  • http://127.0.0.1:<port>/...
  • http://localhost:<port>/...

What fails

Browser Use refuses to navigate to:

  • https://www.google.com/

It fails with this allow/preflight style error:

Browser Use cannot determine if https://www.google.com is allowed. Please try again later or use another source.

Expected behavior

Browser Use should either:

  1. allow normal external navigation when permitted by the current app permission mode, or
  2. surface a clearer permission prompt/error explaining which allow/preflight check failed.

Possibly related

This may be related to Browser Use external navigation / site preflight behavior discussed in:

That issue reports a different low-level error on Windows, but it also points to Browser Use external navigation and site_status / allow preflight behavior.

extent analysis

TL;DR

The issue can be addressed by investigating and potentially modifying the allow/preflight checks in the Browser Use plugin to handle external URLs correctly.

Guidance

  • Review the openai-bundled/browser-use/0.1.0-alpha1 plugin configuration to understand how it handles external URLs and allow/preflight checks.
  • Check the site_status and preflight behavior discussed in the related GitHub issue (https://github.com/openai/codex/issues/19187) to see if it provides insight into the current issue.
  • Test the Browser Use plugin with different external URLs to determine if the issue is specific to certain domains or all external URLs.
  • Consider modifying the plugin to surface a clearer permission prompt or error message when an allow/preflight check fails.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be related to the Browser Use plugin's external navigation and site preflight behavior, but more investigation is needed to determine the root cause.

Recommendation

Apply a workaround by modifying the Browser Use plugin to handle external URLs correctly, as the root cause of the issue is likely related to the plugin's configuration or behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Browser Use should either:

  1. allow normal external navigation when permitted by the current app permission mode, or
  2. surface a clearer permission prompt/error explaining which allow/preflight check failed.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Browser Use blocks external and custom-host URLs with "cannot determine if ... is allowed" on macOS app [1 comments, 2 participants]