What version of the Codex App are you using (From “About Codex” dialog)?
26.1007.21434 (build 13901)
What subscription do you have?
plus
What platform is your computer?
Windows, x64
What issue are you seeing?
Codex detects the installed ChatGPT browser-control extensions for both Chrome and Edge, but cannot list their tabs.
Both browsers report:
Unable to load browser request-header policy. Retry the browser command.
The error persists after retrying and fully restarting Codex Desktop. Browser discovery succeeds, but tab enumeration fails before any page content can be read.
Observed on October 11, 2026.
What steps can reproduce the bug?
- Start Chrome and Edge with the ChatGPT browser-control extensions installed and enabled.
- Open Codex Desktop.
- Ask Codex to check connected browsers and list Chrome tabs.
- Codex detects both browser extensions, but reports:
Unable to load browser request-header policy. Retry the browser command.
- Retry listing Chrome tabs. The same error occurs.
- Fully quit and restart Codex Desktop, then repeat the browser check. Both Chrome and Edge still fail.
The browser-tool calls used were:
await cua.getState();
await cua.listTabs({browser: "3"});
In that test session, browser ID "3" referred to Chrome.
What is the expected behavior?
Codex should list browser tabs, open a public webpage, and read its content through the installed Chrome and Edge extensions.
Additional information
Earlier, browser requests failed with nodeRepl.fetch request failed.
I applied a community proxy workaround:
https://github.com/clen1/codex-browser-fetch-fix
The CUA launcher was backed up and modified to set NODE_USE_ENV_PROXY=1, HTTP/HTTPS proxy variables pointing to the existing local HTTP proxy, and localhost exclusions. Syntax validation passed.
After restarting, Edge successfully listed tabs, opened a public webpage, and read its content.
Chrome’s official extension installation link initially showed “This item is not available.” After switching to a US network exit, I successfully installed the extension.
Subsequent tests detected both Chrome and Edge, but both failed with the request-header policy error. Another full Codex restart did not resolve it. The launcher patch remains present, and the configured local proxy port is listening.
The cause of the new error is unknown. Please note that the current reproduction includes the community launcher modification.
Possibly related:
#21713
#47732
What version of the Codex App are you using (From “About Codex” dialog)?
26.1007.21434 (build 13901)
What subscription do you have?
plus
What platform is your computer?
Windows, x64
What issue are you seeing?
Codex detects the installed ChatGPT browser-control extensions for both Chrome and Edge, but cannot list their tabs.
Both browsers report:
Unable to load browser request-header policy. Retry the browser command.The error persists after retrying and fully restarting Codex Desktop. Browser discovery succeeds, but tab enumeration fails before any page content can be read.
Observed on October 11, 2026.
What steps can reproduce the bug?
Unable to load browser request-header policy. Retry the browser command.The browser-tool calls used were:
await cua.getState();await cua.listTabs({browser: "3"});In that test session, browser ID "3" referred to Chrome.
What is the expected behavior?
Codex should list browser tabs, open a public webpage, and read its content through the installed Chrome and Edge extensions.
Additional information
Earlier, browser requests failed with
nodeRepl.fetch request failed.I applied a community proxy workaround:
https://github.com/clen1/codex-browser-fetch-fix
The CUA launcher was backed up and modified to set NODE_USE_ENV_PROXY=1, HTTP/HTTPS proxy variables pointing to the existing local HTTP proxy, and localhost exclusions. Syntax validation passed.
After restarting, Edge successfully listed tabs, opened a public webpage, and read its content.
Chrome’s official extension installation link initially showed “This item is not available.” After switching to a US network exit, I successfully installed the extension.
Subsequent tests detected both Chrome and Edge, but both failed with the request-header policy error. Another full Codex restart did not resolve it. The launcher patch remains present, and the configured local proxy port is listening.
The cause of the new error is unknown. Please note that the current reproduction includes the community launcher modification.
Possibly related:
#21713
#47732