Codex Chrome Extension connected but page content access is blocked by enterprise network policy

Open 💬 7 comments Opened Jun 9, 2026 by Luke-creat9
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Codex 26.602.71036, released 2026-06-09

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows

What issue are you seeing?

Codex Chrome Extension shows Connected and can read the current Chrome tab title and URL, but it cannot read page content.

This happens even on https://example.com/.

What works:

Codex Chrome Extension shows Connected.
Codex can see the active Chrome tab.
Codex can read the active tab title: Example Domain
Codex can read the active tab URL: https://example.com/

What fails:

Reading visible page text / innerText fails.

Error message, with local file paths removed:

Browser Use rejected this action due to browser security policy.
Reason: Browser Use cannot access https://example.com because enterprise network policy blocks it.

I did not include the full stack trace because it contains local Windows user paths.

What steps can reproduce the bug?

Open Codex desktop app on Windows.
Enable / connect Codex Chrome Extension.
Open Google Chrome.
Manually open https://example.com/.
Confirm that Codex can read the active tab title and URL.
Ask Codex to read the visible page text / innerText from the current tab.
Page content reading fails with:
Browser Use cannot access https://example.com because enterprise network policy blocks it.

Troubleshooting already tried:

Reinstalled the Codex Chrome Extension from Codex settings.
Restarted Chrome.
Restarted Codex.
Checked Chrome Computer Use settings.
Blocked domains list is empty.
Adding allowed domains did not fix the issue.
Tested without navigation/goto/open: manually opened https://example.com/ first, then asked Codex only to read the current tab.

Feedback ID:
019eabba-35ca-7730-a470-18f43d6184ac

What is the expected behavior?

Since the Chrome Extension is connected and https://example.com/ is a basic public web page, Codex should be able to read the visible page text after permission is granted.

Additional information

The issue does not appear to be a connection problem. The Chrome Extension is connected successfully and can read the tab title and URL. The failure only happens when trying to access page content.

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #26298
  • #26264

Powered by Codex Action

Luke-creat9 · 1 month ago

I reviewed the potential duplicate #26298 and the related #24814.

This issue may be related, but my case has one important difference: in my setup, the Codex Chrome Extension backend is connected and can read the active Chrome tab title and URL. The failure only happens when trying to read visible page content / innerText.

This is on a newer Codex version:

  • Codex 26.602.71036, released 2026-06-09
  • Windows
  • ChatGPT Plus
  • Chrome Extension connected
  • Active tab title and URL are readable
  • Page content reading still fails on https://example.com/ with the same enterprise network policy error

So I am leaving this issue open for now in case the newer version / Chrome Extension-specific behavior is useful for debugging. If maintainers prefer to track this under an existing issue, please feel free to mark it as duplicate.

nick-neely · 1 month ago

I'm seeing the same behavior on Windows with Codex 26.609.4994.0.

Setup:

  • Windows Store Codex app: OpenAI.Codex_26.609.4994.0_x64__2p2nqsd0c76g0
  • Running Codex in WSL
  • Chrome plugin enabled
  • Codex Chrome Extension is installed and connected enough to list/claim tabs
  • Enable full CDP Access is currently off
  • https://example.com is explicitly allowlisted

My browser config currently includes:

approval_mode = "never_ask"
full_cdp_access_enabled = false

[origins]
allowed = [ "https://example.com" ]
denied = []

What works:

  • Codex can list my open Chrome tabs.
  • It can see tab titles and URLs.
  • It can claim tabs.

What fails:

As soon as Codex tries to navigate to or read page content from https://example.com, it fails with:

Browser Use rejected this action due to browser security policy. Reason: Browser Use cannot access https://example.com because enterprise network policy blocks it.

I fully restarted Codex and Chrome after changing the browser config, then tested again. The origin stayed allowlisted, but content access still failed with the same enterprise network policy message.

This used to work for me before a recent Codex update. From my side, this does not look like a normal website permission issue, since tab metadata is visible and the origin is explicitly allowed. It looks like the browser policy/content-access layer is rejecting the page after tab discovery succeeds.

Luke-creat9 · 1 month ago

Thanks for confirming. This matches my case.

In my setup, the Chrome Extension can also list / see the active tab, read the tab title and URL, but page content access still fails with the same error:

Browser Use cannot access https://example.com because enterprise network policy blocks it.

I also tried reinstalling the Chrome Extension, restarting Chrome/Codex, and checking the allowed/blocked domain settings. The issue still happens on https://example.com/.

So it looks like the Chrome Extension connection and tab discovery work, but the page-content access layer is still blocked by the browser security policy.

laokewang · 1 month ago
我查看了潜在的重复问题#26298和相关问题#24814。 这个问题可能与此相关,但我的情况有一个重要的区别:在我的设置中,Codex Chrome 扩展程序后端已连接,并且可以读取当前 Chrome 标签页的标题和 URL。只有在尝试读取可见页面内容/innerText 时才会出现故障。 这是在较新版本的Codex中看到的: Codex 26.602.71036,发布于 2026 年 6 月 9 日 视窗 ChatGPT Plus Chrome 扩展程序已连接 当前标签页的标题和 URL 清晰可见。 在https://example.com/上读取页面内容仍然失败,并出现相同的企业网络策略错误。 因此,我暂时保留此问题,以防新版本/Chrome 扩展程序的特定行为对调试有所帮助。如果维护人员希望在现有问题下跟踪此问题,请随时将其标记为重复项。

我也是相同问题

EdmondLu · 1 month ago

I’m seeing what looks like the same issue.

Setup:

  • Codex app version: 26.609.71450
  • Platform: Windows
  • Subscription: ChatGPT Plus
  • App: Codex app for Windows
  • Chrome Extension is installed and connected
  • Codex can see / claim the active Chrome tab
  • Codex can read the tab title and URL

What fails:

When Codex tries to read visible page content / innerText from the current tab, it is rejected with:

Browser Use rejected this action due to browser security policy.
Reason: Browser Use cannot access [URL] because enterprise network policy blocks it.

In my case, the target is an internal/private web app URL that I can open manually in my local Chrome browser. I also tried different Browser Use surfaces, including the in-app browser and the Chrome Extension, and they appear to be blocked by the same policy.

This does not look like a normal website login or permission issue, because the page is accessible from my local Chrome session and the extension connection/tab discovery works. The failure seems to happen specifically at the page-content access layer.

Adding this report because it seems consistent with the behavior described here: Chrome Extension connection works, but page content access is blocked by enterprise network policy.

Kbediako contributor · 23 days ago

I hit the same failure mode on Windows Codex Desktop.

Environment:

  • Codex app/browser bundle: 26.623.42026
  • Codex CLI after repair: 0.142.3
  • Codex home: %USERPROFILE%\.codex

Symptom:
Browser Use failed for every site with:
"Browser Use cannot access https://... because enterprise network policy blocks it."

Findings:

  • configRequirements/read returned requirements: null, so this was not a real managed enterprise policy.
  • DNS and TCP 443 were fine.
  • CODEX_CLI_PATH in both the process/user environment and %USERPROFILE%\.codex\config.toml pointed to a missing path:

...\vendor\x86_64-pc-windows-msvc\codex\codex.exe

  • The actual installed CLI path was:

...\vendor\x86_64-pc-windows-msvc\bin\codex.exe

Fix:

  • Updated %USERPROFILE%\.codex\config.toml [mcp_servers.node_repl.env].CODEX_CLI_PATH
  • Updated the user-level CODEX_CLI_PATH environment variable
  • Fully exited and reopened Codex

Result:
Browser Use recovered. It could navigate to https://asabeko.com/, read the page title/DOM, scroll, and click the menu.

Extra note:
A config-only fix did not survive until the user-level environment variable was also corrected, because Codex appeared to regenerate the stale value on app restart. Hopefully this helps!