Its theme's rank, 14 days: 3 on the Codex sheet
11 people reported

All time, since Oct 18, including 5 thumbs-up on GitHub.

Browser disabled despite toggle

“Browser discovery fails with the error above.”

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/19054/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

Growing. 5 reports and thumbs-up in the last 7 days and 2 the week before. A workaround is known.

Browser use reports disabled in Work settings while toggle is on. Browser tools return "Local browser use is disabled in Work settings" and find no browsers, although Settings → Browser shows the toggle enabled.

Is this your bug?

File my report
Where
Built-in browser control
Error text
Local browser use is disabled in Work settings
Versions
26.1013.40934
Platforms
Windows
How bad
Breaks a normal workflow.

Part of: Browser control fails to connect36 bugs

  1. Request-header policy load failure16 people
  2. Chrome extension not detected16 people
  3. Browser control times out12 people
  4. Chrome tab operations fail8 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

Not quite your bug?

  1. Allowed site still denied10 people

Original reports6, newest first

  1. Codex desktop browser access blocked by Work settings errorOn GitHub#59181
  2. Browser enabled but Chrome and Edge fail with “Local browser use is disabled in Work settings”On GitHub#58594
  3. Local browser use is disabled in Work settingsOn GitHub#56645
  4. Windows desktop: CUA browser becomes disabled mid-session; app restart restores accessOn GitHub#56542
  5. CODEX BUG: Built-in browser access intermittently blocked by “Local browser use is disabled in Work settings”On the forum#1408172
  6. Windows: browser reports disabled in Work settings while Browser toggle is enabled; restarting app restores accessOn GitHub#54989

Do you work on Codex?

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