8 people reported
All time, since Sep 14, including 2 thumbs-up on GitHub.
Chrome tab operations fail
“Chrome can be discovered as an extension-backed browser, but listing tabs or opening a requested page fails with nodeRepl.fetch request failed.”
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/13669/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
Chrome tab listing and opening fail with nodeRepl.fetch on Windows. Chrome is discovered and the extension sidebar works, but Codex cannot list, create or bind Chrome tabs.
Is this your bug?
File my report- Where
- Chrome plugin
- Error text
nodeRepl.fetch request failed- Versions
- 26.908.9136.0 to 26.930.7945.0
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Part of: Browser control fails to connect36 bugs
- Request-header policy load failure16 people
- Chrome extension not detected16 people
- Browser control times out12 people
- Browser disabled despite toggle11 people
- Browser access host unavailable12 people
- Browser tab control fails4 people
- Agent finds no browser5 people
- Browser access host unavailable9 people
- Chrome tab control timeoutMs error7 people
- Browser unavailable to assistant4 people
Show all 35Show only the largest 10
- Embedded browser unusable when sidebar keeps client-new-thread conversation ID5 people
- Browser tab access lost5 people
- In-app browser not available4 people
- Browser service module missing3 people
- In-app browser policy check fails2 people
- Browser tools missing in chat4 people
- Chrome connection drops2 people
- Browser ID unavailable2 people
- Built-in Browser unreachable2 people
- Chrome native host not registered2 people
- Chrome tab listing fails2 people
- Chrome not available to runtime2 people
- Chrome debugger detaches, CDP timeouts3 people
- Browser Use policy check fails3 people
- Side-panel browser control fails2 people
- Chrome page loads stall while browser control resolves paused document responses4 people
- Browser access host unavailable15 people
- Chrome missing from @ menu3 people
- Browser context error in Chrome4 people
- Browser access host unavailable3 people
- Lost cua_repl browser tool2 people
- Chrome browser access unavailable3 people
- Browser extension connection lost5 people
- Browser.list_tabs context error4 people
- Browser reported disabled in chat4 people
Original reports7, newest first
- Windows desktop app cannot connect to Chrome: nodeRepl.fetch request failedOn GitHub#56487
- Windows 浏览器连接持续失败：nodeRepl.fetch request failedOn GitHub#56485
- [Windows][Codex App 26.930.7945.0] Chrome discovered but tab enumeration and creation fail with nodeRepl.fetch request failedOn GitHub#51363
- [Windows][Desktop] Chrome discovered but list/open tabs fail with nodeRepl.fetch on 26.915.4065.0On GitHub#47732
- Windows Codex desktop cannot connect to Chrome: nodeRepl.fetch request failedOn GitHub#46743
- [macOS, 26.915.31945] Chrome discovery succeeds but tab enumeration fails after ~30s with nodeRepl.fetch request failedOn GitHub#46609
- [Windows 11][26.908.9136.0] Chrome backend is discoverable but tab operations fail with nodeRepl.fetch request failedOn GitHub#45576