16 people reported

All time, since Sep 15, including 1 thumbs-up on GitHub.

Request-header policy load failure

“Direct cua.createBrowserTab(...) calls fail with the same policy error before a page can be inspected.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/9319/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 7 a week at the mid-October peak.

Browser control fails loading request-header policy in Chrome and Edge. Browser discovery or tab listing fails before page content can be read, and the error persists after retrying and fully restarting Codex Desktop.

Is this your bug?

File my report
Where
Browser control extension
Error text
Unable to load browser request-header policy. Retry the browser command.
Versions
0.162.0 to 26.1007.21434
Platforms
Linux, macOS, Windows
How bad
Some reports say it blocks them completely.

Part of: Browser control fails to connect36 bugs

  1. Chrome extension not detected16 people
  2. Browser control times out12 people
  3. Chrome tab operations fail8 people
  4. Browser disabled despite toggle11 people
  5. Browser access host unavailable12 people
  6. Browser tab control fails4 people
  7. Agent finds no browser5 people
  8. Browser access host unavailable9 people
  9. Chrome tab control timeoutMs error7 people
  10. Browser unavailable to assistant4 people
Show all 35Show only the largest 10
  1. Embedded browser unusable when sidebar keeps client-new-thread conversation ID5 people
  2. Browser tab access lost5 people
  3. In-app browser not available4 people
  4. Browser service module missing3 people
  5. In-app browser policy check fails2 people
  6. Browser tools missing in chat4 people
  7. Chrome connection drops2 people
  8. Browser ID unavailable2 people
  9. Built-in Browser unreachable2 people
  10. Chrome native host not registered2 people
  11. Chrome tab listing fails2 people
  12. Chrome not available to runtime2 people
  13. Chrome debugger detaches, CDP timeouts3 people
  14. Browser Use policy check fails3 people
  15. Side-panel browser control fails2 people
  16. Chrome page loads stall while browser control resolves paused document responses4 people
  17. Browser access host unavailable15 people
  18. Chrome missing from @ menu3 people
  19. Browser context error in Chrome4 people
  20. Browser access host unavailable3 people
  21. Lost cua_repl browser tool2 people
  22. Chrome browser access unavailable3 people
  23. Browser extension connection lost5 people
  24. Browser.list_tabs context error4 people
  25. Browser reported disabled in chat4 people

Original reports15, newest first

  1. Windows Chrome connection fails: Unable to load browser request-header policy App version:On GitHub#54367
  2. Linux: Chrome discovered but browser policy initialization POST returns Cloudflare 403 for oaistatsig.comOn GitHub#54342
  3. Browser connection cannot load request-header policy across Chrome, Edge, and BraveOn GitHub#54339
  4. Codex Windows Cloudflare 403 — Browser policy initialization blockedOn GitHub#54327
  5. Windows browser bridge fails to load request-header policy in ChatGPT desktopOn GitHub#53317
  6. [Windows 26.1007.21434] Chrome Browser Use fails loading request-header policy after kernel resetOn GitHub#53117
  7. Browser control fails with “Unable to load browser request-header policy” in Chrome and Edge on WindowsOn GitHub#53048
  8. [Windows] Chrome extension reads webpages but interaction fails: Unable to load browser request-header policyOn GitHub#53009
  9. [Windows] Unable to load browser request-header policy: Desktop overwrites browser MCP proxy env on restartOn GitHub#52956
  10. Windows Chrome request-header policy initialization still fails after full restart and targeted heartbeat-loop mitigationOn GitHub#52502
Show all 15Show only the newest 10
  1. [macOS] Chrome browser control fails before page access with request-header policy error (26.1002.52244)On GitHub#52080
  2. Windows browser control fails during policy initializationOn GitHub#48763
  3. Windows Work @Chrome fails to load browser request policy while @Browser worksOn GitHub#45990
  4. Windows: browser request-header policy failure persists after restarts; native fallback cannot verify URLOn GitHub#45910
  5. Chrome connection fails: Unable to load browser request-header policyOn GitHub#45678

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.