Codex Browser Use and Mobile Remote Connection Stopped Working After App Update

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

26.721.4979.0

What subscription do you have?

plus

What platform is your computer?

windows 11

What issue are you seeing?

I currently have three computers, all running Windows, but each computer has a different version of the Codex App installed.
My primary computer, which I mainly use for software development and other daily work, is experiencing a serious issue. Possibly after Codex was updated around July 4, 2026, Browser Use stopped working completely on this computer.
Whether I explicitly instruct Codex to visit a specific cloud service provider or website to retrieve information, or ask it to operate the browser, it reports that access is blocked. The error message is consistently similar to:
“Codex Browser Use was blocked by enterprise network policy…”

As a result, the browser functionality is completely unusable on this computer.
The Codex version currently installed on my primary computer is:
26.721.4979.0
I have tried numerous troubleshooting methods without success, so I suspect the issue may be related to a Codex version update.
I tested the same browser-related functionality on two other Windows computers. Both can access the relevant websites, control the browser/computer, and complete tasks normally. Their Codex versions are:
26.715.9868.0
26.715.7063.0
Based on these results, I strongly suspect that the newer Codex version installed on my primary computer may have caused Browser Use to stop working.
There is also another potentially related issue on this computer. Previously, I was able to connect to and remotely control Codex on this computer from my phone. However, this functionality also stopped working recently, although I do not remember the exact date when the problem began.
The mobile connection can no longer reliably wake or establish the remote Codex session. In most cases, the computer cannot be reached or awakened remotely; in other cases, the connection attempt simply fails. This has been a persistent problem, and I am now completely unable to use the mobile remote connection feature with this computer.
I reported the Browser Use issue last week through the Help and Feedback channels in Codex. However, I did not include the specific version information or the mobile remote connection issue at the time, and I have not yet received a response.
I am now submitting these additional details and version numbers in the hope that they will help your team identify the root cause more accurately and resolve the issue as soon as possible. These problems are severely affecting my daily work and my ability to use Codex effectively.

To clarify, Codex is running natively on Windows on the affected computer, not in WSL mode. The current session uses Windows PowerShell and native Windows paths. The @Browser capability can be initialized successfully, but navigation is rejected with an “enterprise network policy blocked” error when it attempts to access the target website. Therefore, this does not appear to be the known limitation affecting @Browser or @Chrome in Windows WSL mode.

What steps can reproduce the bug?

Feedback ID: 019f8021-926b-7a50-ac5c-bc11dd1bb70f

What is the expected behavior?

Codex Browser Use and @Chrome should be available when Codex is running natively on Windows. When I ask Codex to visit a normal public website or operate the browser, it should open the requested website and complete the task, as it does on my other two Windows computers.
It should not reject all browser navigation requests with an “enterprise network policy blocked” error, especially when the computer is not running Codex in WSL mode.

Additional information

The affected computer is running Codex natively on Windows, not in WSL mode. The current sessions use Windows PowerShell and native Windows paths.
The @Browser capability can be initialized successfully. However, when Codex attempts to navigate to a website, the request is rejected with an error stating that Browser Use is blocked by an enterprise network policy.
The affected Codex App version is:
26.721.4979.0
I tested the same browser functionality on two other Windows computers, and both work normally. Their Codex App versions are:
26.715.9868.0
26.715.7063.0
The issue appears to have started around July 4, 2026, possibly after the affected computer received a Codex App update.
I have already checked the relevant Codex permissions, Windows Firewall settings, VPN/proxy configuration, and browser settings, but the issue persists.
There may also be a related connectivity issue: I was previously able to connect to and remotely control Codex on this computer from my phone. Recently, the mobile connection has been unable to wake or connect to the computer, or the connection attempt fails. I do not remember the exact date when this second issue started.
I previously submitted this issue through Codex Help and Feedback, but that report did not include the detailed version comparison above.