Windows Codex App: Browser Use IAB navigation to baidu.com rejected by enterprise network policy despite enabled Browser/Chrome plugins
What version of the Codex App are you using?
Codex Windows Store app: 26.527.7698.0
Package:
OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0
Codex CLI:
codex-cli 0.136.0
Bundled plugin versions from codex plugin list:
browser@openai-bundled installed, enabled 26.527.60818
chrome@openai-bundled installed, enabled 26.527.60818
computer-use@openai-bundled installed, enabled 26.527.60818
What subscription do you have?
ChatGPT Plus/Pro account context in Codex app. Please check submitted thread metadata if available.
What platform is your computer?
Windows x64
Microsoft Windows NT 10.0.26100.0
Microsoft Windows 10.0.26100
What issue are you seeing?
Using the bundled Browser plugin in the Windows Codex app, the agent attempted to open Baidu through the in-app browser (iab) backend:
const { setupBrowserRuntime } = await import("C:/Users/shuaiyang5/.codex/plugins/cache/openai-bundled/browser/26.527.60818/scripts/browser-client.mjs");
await setupBrowserRuntime({ globals: globalThis });
globalThis.browser = await agent.browsers.get("iab");
await browser.nameSession("🔎 百度");
await (await browser.capabilities.get("visibility")).set(true);
globalThis.tab = await browser.tabs.new();
await tab.goto("https://www.baidu.com/");
The action was rejected before navigation completed:
Browser Use rejected this action due to browser security policy. Reason: Browser Use cannot access https://www.baidu.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. Proceed only with a materially safer alternative that does not require this blocked browser action; if none exists, stop and request user input.
This looks related to #24814 and #24969, but this report is from a newer app version (26.527.7698.0) where both Browser and Chrome plugins are installed and enabled.
Browser backend diagnostics
Running agent.browsers.list() in the same session shows both the Chrome extension backend and the in-app browser backend are visible:
{
"browsers": [
{
"name": "Chrome",
"type": "extension",
"metadata": {
"extensionId": "hehggadaopoacecdllhhajmbjkdcmajg",
"extensionInstanceId": "216ed274-76cf-42f2-8fbd-dfbb44f472d3",
"profileName": "您的 Chrome",
"profileIsLastUsed": "false",
"profileOrdering": "0"
}
},
{
"name": "Codex In-app Browser",
"type": "iab",
"metadata": {
"codexAppBuildFlavor": "prod",
"codexAppSessionId": "d008a878-01dc-4206-9ab5-297916752f46",
"codexSessionId": "019e90a5-9dd2-7183-9cdb-238b68ecb404"
}
}
]
}
Request metadata observed in the Node REPL did not include an explicit x-codex-browser-use-available-backends entry, only normal turn metadata:
{
"threadId": "019e90a5-9dd2-7183-9cdb-238b68ecb404",
"x-codex-turn-metadata": {
"model": "gpt-5.5",
"sandbox": "none",
"session_id": "019e90a5-9dd2-7183-9cdb-238b68ecb404",
"thread_id": "019e90a5-9dd2-7183-9cdb-238b68ecb404",
"thread_source": "user"
}
}
Steps to reproduce
- Start Codex Windows Store app
26.527.7698.0. - Confirm
browser@openai-bundledandchrome@openai-bundledare installed/enabled. - Ask the agent to use
@Browserto openhttps://www.baidu.com/. - The agent bootstraps the bundled Browser plugin via
node_repl, getsiab, creates a tab, and callstab.goto("https://www.baidu.com/"). - Browser Use rejects the navigation with an enterprise network policy block.
Expected behavior
Browser Use should either:
- navigate the in-app browser to
https://www.baidu.com/, or - if this URL is intentionally blocked by policy, expose a user-visible reason/policy source that explains why.
Actual behavior
Browser Use reports an enterprise network policy block for https://www.baidu.com/ even though this appears to be the same class of Windows Browser Use runtime/policy issue already reported for ordinary network URLs in #24814 and #24969.
Additional context
This report is not asking for policy circumvention. The confusing part is that the error text presents the block as an enterprise policy decision, while similar public reports show this happening on Windows Codex app builds even for normal web targets such as https://example.com and localhost.
Related issues:
- #24814
- #24969
- #21781
- #25253
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks. This does appear related to #24969 and #24814, but I am keeping this open for now because this report captures a slightly different/newer state:
26.527.7698.0.browser@openai-bundledandchrome@openai-bundledare both installed and enabled at26.527.60818.agent.browsers.list()can see both backends:Chromewithtype: "extension"Codex In-app Browserwithtype: "iab"https://www.baidu.com/is still rejected asenterprise network policybefore navigation completes.So this may no longer be only the earlier “backend not exposed” failure mode. It looks like the policy/navigation block can still occur even when the browser backends are visible in the runtime.
If maintainers prefer, this can be closed as a duplicate of #24969, but I wanted to preserve the newer-version diagnostics here because they may help narrow the remaining failure mode.
Additional local diagnostics:
The machine has normal network access outside Browser Use:
Chrome plugin diagnostics are all healthy:
The current thread permission state is not
networkAccess: false; global state shows this thread as:A more specific failure was found in the Node REPL internal fetch path:
returns:
Local
~/.codex/config.tomlhad a stale/nonexistentCODEX_CLI_PATH:That file does not exist. The actual bundled CLI exists at:
and reports:
I updated
CODEX_CLI_PATHlocally to the real bundled CLI path, but the currently runningnode_replprocess still reports the samefailed to start codex app-servererror, presumably because it was already launched with the stale path. A full Codex app restart may be required before retesting.This suggests the Browser Use
enterprise network policyerror can be downstream of app-server startup/config resolution failure: Browser Use attempts to evaluate site/network policy, internal app-server startup fails due to a stale CLI path, and the policy read path falls into a deny result shown ascodex-network-policy/ enterprise policy.