RAP Sheet home
Install the bug reporting skill
Rank, 14 days: 3 on the Codex sheet
180 people reported

All time, since Sep 14, including 55 thumbs-up on GitHub.

Browser control fails to connect

“The official ChatGPT Chrome extension is installed and enabled in the active Chrome profile, but the desktop app cannot detect or connect to it.”

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/themes/142/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. 68 reports and thumbs-up in the last 7 days and 33 the week before.

36 bugs in this theme

  1. Request-header policy load failureNo workaround yet16 people
  2. Chrome extension not detectedNo workaround yet16 people
  3. Browser access host unavailableNo workaround yet15 people
  4. Browser control times outNo workaround yet12 people
  5. Browser access host unavailableNo workaround yet12 people
  6. Browser disabled despite toggleHas a workaround11 people
  7. Browser access host unavailableNo workaround yet9 people
  8. Chrome tab operations failNo workaround yet8 people
  9. Chrome tab control timeoutMs errorNo workaround yet7 people
  10. Agent finds no browserNo workaround yet5 people
Show all 36Show only the largest 10
  1. Embedded browser unusable when sidebar keeps client-new-thread conversation IDNo workaround yet5 people
  2. Browser tab access lostHas a workaround5 people
  3. Browser extension connection lost5 people
  4. Browser tab control failsNo workaround yet4 people
  5. Browser unavailable to assistantNo workaround yet4 people
  6. In-app browser not availableNo workaround yet4 people
  7. Browser tools missing in chatHas a workaround4 people
  8. Chrome page loads stall while browser control resolves paused document responsesHas a workaround4 people
  9. Browser context error in ChromeNo workaround yet4 people
  10. Browser.list_tabs context error4 people
  11. Browser reported disabled in chat4 people
  12. Browser service module missingNo workaround yet3 people
  13. Chrome debugger detaches, CDP timeoutsHas a workaround3 people
  14. Browser Use policy check failsHas a workaround3 people
  15. Chrome missing from @ menuNo workaround yet3 people
  16. Browser access host unavailableHas a workaround3 people
  17. Chrome browser access unavailableNo workaround yet3 people
  18. In-app browser policy check failsNo workaround yet2 people
  19. Chrome connection dropsNo workaround yet2 people
  20. Browser ID unavailableHas a workaround2 people
  21. Built-in Browser unreachableNo workaround yet2 people
  22. Chrome native host not registeredNo workaround yet2 people
  23. Chrome tab listing failsNo workaround yet2 people
  24. Chrome not available to runtimeNo workaround yet2 people
  25. Side-panel browser control failsNo workaround yet2 people
  26. Lost cua_repl browser toolNo workaround yet2 people

What's included

  • Browser actions fail with "Unable to load browser request-header policy", sometimes alongside a Cloudflare 403 from the policy endpoint
  • Chrome or Edge is discovered but tab listing fails with "nodeRepl.fetch request failed", or logs show "No ChatGPT browser route is available"
  • Chrome is missing from discovery ("Browser is not available: chrome", only MCP Apps listed), or settings report the extension "Not installed" with repair controls disabled
  • Native host registration missing or browser-client not trusted; Chrome side panel errors such as "Sheep MCP session closed" or "requires the originating browser context"
  • Chrome control intermittently drops with "Debugger unattached" and CDP command timeouts
  • Browser discovery lists only Codex MCP Apps or no browsers, and binding returns "Browser is not available: iab" (sometimes also for Chrome), with logs showing "No ChatGPT browser route is available for browser session"

Not included

  • Native Windows Computer Use stopping on window-state requests because it cannot determine the browser URL
  • General Computer Use control of non-browser desktop apps

Original reports131, newest first

  1. The browser access host is unavailableOn GitHub#60151
  2. [macOS][CLI 0.167.0] Chrome Browser Use fails with "The browser access host is unavailable" while desktop worksOn GitHub#60130
  3. [Windows][CLI 0.167.0 / IDEA ACP] Chrome extension access fails: browser access host unavailable; desktop worksOn GitHub#60127
  4. [Windows] Chrome extension installed but Chrome is missing from Codex browser list and @ menuOn GitHub#60110
  5. [macOS arm64][CLI 0.167.0][Edge] Browser access host unavailable; native app control succeedsOn GitHub#60071
  6. mrOn GitHub#60036
  7. [CLI 0.167.0][macOS] Chrome plugin still fails: browser access host unavailable — please fix CLI support and stop the restart loopOn GitHub#59799
  8. [macOS Desktop 26.1029.70936] Built-in browser tab control times out with “No ChatGPT browser route”On GitHub#59663
  9. [Windows] In-app browser tab attaches to temporary chat and IAB discovery failsOn GitHub#59660
  10. [macOS arm64][CLI 0.166.0] codex exec cannot use the ChatGPT Chrome extension: "The browser access host is unavailable" (desktop works)On GitHub#59592
Show the newest 100 of 131Show only the newest 10
  1. Browser Use unavailable in an existing Codex chat while in-app browser tabs remain openOn GitHub#59583
  2. Browser Control fails with undefined timeoutMs when attaching to Chrome tabs on UbuntuOn GitHub#59574
  3. Codex Desktop for macOS: In-App Browser and Chrome Extension Control Time OutOn GitHub#59543
  4. Codex Desktop for macOS: In-App Browser and Chrome Extension Control Time OutOn GitHub#59542
  5. Codex desktop Chrome tab control fails with undefined timeoutMs after successful connectionOn GitHub#59494
  6. CLI browser control fails: “The browser access host is unavailable”; desktop worksOn GitHub#59456
  7. [macOS][Codex CLI][Chrome] CUA tab creation/getTab fails with undefined timeoutMs despite working extension tunnelOn GitHub#59437
  8. 6.1 Terra reporting that Chrome automation connection disconnected when I have done nothingOn GitHub#59402
  9. Browser Use: browser.user is unavailable when reusing IAB tabs across turnsOn GitHub#59382
  10. [Windows][CLI 0.166.0] App-managed Edge extension works in desktop but CLI reports browser access host unavailableOn GitHub#59334
  11. [Windows CLI] Previously working Chrome access now fails with browser access host unavailable; Desktop still worksOn GitHub#59300
  12. [Linux][Chrome] Page actions fail immediately with undefined timeoutMs; discovery works (Desktop 26.1013.31256)On GitHub#59276
  13. Thread running during an app update loses the cua_repl browser tool permanentlyOn GitHub#59191
  14. Codex desktop browser access blocked by Work settings errorOn GitHub#59181
  15. Desktop browser use: browser IDs change on reconnect and break bindings that the docs say to reuseOn GitHub#59144
  16. Windows IntelliJ Codex CLI cannot access Chrome browser bridgeOn GitHub#59142
  17. [macOS] Chrome missing from Work chat @ menu even though the extension is installed and enabledOn GitHub#59101
  18. built-in browser access fails between chat messagesOn GitHub#59005
  19. [Windows][IDEA ACP] Chrome extension access fails when Codex starts from IntelliJ IDEAOn the forum#1412145
  20. [Windows 11][VS Code] Native @Browser fails with "The browser access host is unavailable" while Desktop Browser worksOn GitHub#58916
  21. Windows desktop: temporary sidebar conversationId persists for real local chat; browser control tools disappearOn GitHub#58785
  22. Codex CLI cannot connect to Google ChromeOn GitHub#58772
  23. Browser enabled but Chrome and Edge fail with “Local browser use is disabled in Work settings”On GitHub#58594
  24. Browser document interception can strand CDP refresh/read on SunoOn GitHub#58576
  25. [macOS][26.1027.30824] Visible in-app browser cannot bind: Browser is not available: iabOn GitHub#58419
  26. [macOS][IAB] Browser access fails across turns with “browser.user is unavailable”; reset restores accessOn GitHub#58386
  27. CLI 0.166.0 cannot access Chrome extension: "The browser access host is unavailable"On GitHub#58331
  28. [macOS][IAB] Preserved tab fails across turns with browser.user is unavailable on 26.1027.30824On GitHub#58236
  29. Windows desktop embedded browser times out when sidebar retains client-new-thread IDOn GitHub#58173
  30. macOS: resumed chat loses cua_repl browser controls after app restart despite browser backend being readyOn GitHub#57826
  31. Windows Edge browser extension regression after CLI 0.163.0On GitHub#57801
  32. [Windows desktop] Side browser opens, but control initialization fails due to missing browser-service.mjsOn GitHub#57583
  33. Chrome browser connection fails: “Browser access requires the originating browser context”On GitHub#57523
  34. Chrome extension Work side chat loses originating browser context despite healthy native bridge and full app/browser restartOn GitHub#57482
  35. macOS: browser reports disabled in an existing chat after restart while enabled and other chats workOn GitHub#57190
  36. [Windows app] In-app browser tools disappear mid-chat while active-tab context remainsOn GitHub#57143
  37. macOS Intel 26.1021.31345: Chrome side panel connects, but supported runtime exposes only mcpappsOn GitHub#56958
  38. Browser automation unavailable: “The browser access host is unavailable”On GitHub#56928
  39. [Windows] Chrome and IAB unavailable: no browser route on 26.1021.31345 after reinstall and fresh chatOn GitHub#56873
  40. [Windows][26.1021.31345] IAB page renders, but CUA reports Browser is not available: iab in fresh chatsOn GitHub#56755
  41. [Windows Desktop 26.1013.3656.0] IAB tab remains owned by client-new-thread, preventing Browser Use attachmentOn GitHub#56706
  42. Local browser use is disabled in Work settingsOn GitHub#56645
  43. [Windows] Computer Use shows Manage but Chrome native host registration is missingOn GitHub#56603
  44. Chrome control missing in ChatGPT desktop Codex despite enabled extensionOn GitHub#56565
  45. Windows desktop: CUA browser becomes disabled mid-session; app restart restores accessOn GitHub#56542
  46. Windows desktop app cannot connect to Chrome: nodeRepl.fetch request failedOn GitHub#56487
  47. Windows 浏览器连接持续失败：nodeRepl.fetch request failedOn GitHub#56485
  48. Chrome unavailable to agent despite working extension and side chat on WindowsOn GitHub#55814
  49. CODEX BUG: Built-in browser access intermittently blocked by “Local browser use is disabled in Work settings”On the forum#1408172
  50. [Windows] Chrome Browser Use repeatedly loses debugger attachment and times out after extension reinstall (26.1013.40934)On GitHub#55554
  51. Browser access problemOn GitHub#55240
  52. Windows desktop: Edge tab mention unavailable; browser inventory contains only MCP Apps despite enabled extensionOn GitHub#55223
  53. [macOS] Browser tools return “The browser access host is unavailable” while in-app tab worksOn GitHub#55173
  54. [macOS][Chrome Browser Use] Auth0 page loading stalls with paused-document-response guard; Cancel reportedly releases loadingOn GitHub#55166
  55. Windows: Chrome unavailable to browser tools despite installed and enabled extensionOn GitHub#55018
  56. Windows: browser reports disabled in Work settings while Browser toggle is enabled; restarting app restores accessOn GitHub#54989
  57. [Windows desktop] CUA discovers only MCP Apps; Chrome and in-app Browser missing in existing and fresh chatsOn GitHub#54968
  58. Chrome side-panel browser skills stopped working after new layout: “Sheep MCP session closed: RPC INTERNAL”On GitHub#54612
  59. Windows desktop: previously working long-lived chat loses browser tools; fresh chat restores accessOn GitHub#54545
  60. [macOS / Chrome side panel / Work] Browser initialization fails after about one minute with "Sheep MCP session closed: RPC INTERNAL"On GitHub#54527
  61. macOS desktop Chat mode: Browser.list_tabs fails with "Browser access requires the originating browser context"On GitHub#54520
  62. Browser extension access stopped working after previously working — RPC INTERNAL and “coming soon”On GitHub#54484
  63. Windows browser control still times out after Browser reinstall: Chrome tab listing fetch failure and IAB external-page hangsOn GitHub#54481
  64. Windows Chrome connection fails: Unable to load browser request-header policy App version:On GitHub#54367
  65. Linux: Chrome discovered but browser policy initialization POST returns Cloudflare 403 for oaistatsig.comOn GitHub#54342
  66. Browser connection cannot load request-header policy across Chrome, Edge, and BraveOn GitHub#54339
  67. Codex Windows Cloudflare 403 — Browser policy initialization blockedOn GitHub#54327
  68. 01a13fbd-4b1c-72e3-aa31-dcc4fad3bf78On GitHub#54297
  69. Codex built-in Browser connection diagnosisOn GitHub#54244
  70. Integrated browser unavailable on macOS: native pipe startup failsOn GitHub#54198
  71. macOS: Chrome extension installed and enabled but desktop app reports Not installedOn GitHub#54067
  72. the desktop app can't connect to the built in browserOn GitHub#53993
  73. macOS Chrome CUA: retained browser IDs become unavailable across calls while the extension and tab remainOn GitHub#53700
  74. Chrome extension cannot connect to desktop app; “Open the app” does not establish connectionOn GitHub#53641
  75. macOS: built-in browser is visible but runtime reports Browser is not available: iabOn GitHub#53425
  76. Windows browser bridge fails to load request-header policy in ChatGPT desktopOn GitHub#53317
  77. Windows 26.1007.21434: browser-control subagent sees no browsers while IAB pages render and Chrome setup shows ManageOn GitHub#53306
  78. [Windows] Chrome plugin fails: browser-client not trusted and Native Host registration missingOn GitHub#53246
  79. Windows Codex App cannot list Chrome tabs: browser request-header policy fails to load; CLI can operate webpagesOn GitHub#53242
  80. [Windows 26.1007.21434] Chrome Browser Use fails loading request-header policy after kernel resetOn GitHub#53117
  81. Desktop browser runtime cannot discover Chrome after restart despite passing extension diagnosticsOn GitHub#53058
  82. Windows browser control fails across Chrome, Edge and in-app browser after update; nodeRepl.fetch request failedOn GitHub#53056
  83. Browser control fails with “Unable to load browser request-header policy” in Chrome and Edge on WindowsOn GitHub#53048
  84. [Windows] Chrome extension reads webpages but interaction fails: Unable to load browser request-header policyOn GitHub#53009
  85. [Windows] Unable to load browser request-header policy: Desktop overwrites browser MCP proxy env on restartOn GitHub#52956
  86. [Windows] Chrome browser integration repeatedly disconnects during sustained Codex automationOn GitHub#52953
  87. Windows Codex Desktop: Browser automation fails with nodeRepl.fetch request failedOn GitHub#52898
  88. In-app browser unavailable and Chrome extension won’t connectOn GitHub#52619
  89. Windows Chrome request-header policy initialization still fails after full restart and targeted heartbeat-loop mitigationOn GitHub#52502
  90. @Chrome: session route captured then revoked within ~374 ms by a client-new-thread browser host (Desktop 26.1002.52244)On GitHub#52472

Do you work on Codex?

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

Claim a tool