codex - 💡(How to fix) Fix Windows Codex App: Browser Use blocked by enterprise network policy even for example.com

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…

Error Message

Observed error:

Root Cause

Browser Use rejected this action due to browser security policy. Reason: Browser Use cannot access https://example.com because enterprise network policy blocks it. The agent must not attempt to achieve the same outcome via workaround, indirect execution, raw CDP or browser commands, alternate browser surfaces, or policy circumvention.

Fix Action

Fix / Workaround

Browser Use rejected this action due to browser security policy. Reason: Browser Use cannot access https://example.com because enterprise network policy blocks it. The agent must not attempt to achieve the same outcome via workaround, indirect execution, raw CDP or browser commands, alternate browser surfaces, or policy circumvention.

Code Example

Browser Use rejected this action due to browser security policy. Reason: Browser Use cannot access https://example.com because enterprise network policy blocks it. The agent must not attempt to achieve the same outcome via workaround, indirect execution, raw CDP or browser commands, alternate browser surfaces, or policy circumvention.

---

Allow the node_repl MCP server to run tool "js"?

---

title: Example Domain

---

Codex 9PLM9XGG6VKS 26.519.11010.0 msstore
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using?

26.519.11010.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Windows x64, Microsoft Store Codex app.

What issue are you seeing?

The Codex in-app browser pane can be opened manually and the user can manually navigate it to external sites such as https://example.com.

However, the agent cannot navigate, read, or inspect even https://example.com through Browser Use / node_repl. Every attempt fails with an enterprise network policy block.

The visible in-app browser is open and can show https://example.com, but agent-side access to the current page is still blocked.

Observed error:

Browser Use rejected this action due to browser security policy. Reason: Browser Use cannot access https://example.com because enterprise network policy blocks it. The agent must not attempt to achieve the same outcome via workaround, indirect execution, raw CDP or browser commands, alternate browser surfaces, or policy circumvention.

This also happens for https://www.royalroad.com, but it is not specific to Royal Road because https://example.com fails the same way.

The user also sees repeated approval prompts like:

Allow the node_repl MCP server to run tool "js"?

After approving, Browser Use still cannot access the page.

What steps can reproduce the bug?

  1. Open Codex Windows App.
  2. Open the in-app browser pane.
  3. Manually navigate the pane to https://example.com.
  4. Ask the agent to read the current page title or DOM.
  5. The agent attempts Browser Use via node_repl and receives an enterprise network policy block.
  6. In a new Codex conversation, repeat the same test. The failure is the same.

Expected behavior

If the in-app browser pane is manually open on https://example.com, Browser Use should be able to read the page title and DOM snapshot, or at least the current URL/title, assuming the user approves the node_repl tool call.

Expected result:

title: Example Domain

Actual behavior

Browser Use reports that https://example.com is blocked by enterprise network policy, even though the in-app browser pane itself can display the page when the user navigates manually.

Additional information

  • Reproduces in both an existing conversation and a new conversation.
  • Restarting Codex did not fix it.
  • This appears after a Codex app update.
  • Current installed package reported by winget list Codex:
Codex 9PLM9XGG6VKS 26.519.11010.0 msstore
  • This breaks workflows that depend on Browser Use automation in the in-app browser.

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

If the in-app browser pane is manually open on https://example.com, Browser Use should be able to read the page title and DOM snapshot, or at least the current URL/title, assuming the user approves the node_repl tool call.

Expected result:

title: Example Domain

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 Windows Codex App: Browser Use blocked by enterprise network policy even for example.com