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

All time, since Oct 13.

Browser ID unavailable

“A fresh inventory still shows the same extension instance and the same tab T, with a new browser ID B.”

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

Browser IDs become unavailable after reconnect, breaking retained bindings. Retained browser IDs from the CUA browser APIs fail with "Browser is not available" while the extension and tab remain, and a fresh listing shows a new ID.

Is this your bug?

File my report
Where
Chrome browser use
Error text
Browser is not available: A
Versions
26.1023.6621
Platforms
macOS, 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 disabled despite toggle11 people
  6. Browser access host unavailable12 people
  7. Browser tab control fails4 people
  8. Agent finds no browser5 people
  9. Browser access host unavailable9 people
  10. Chrome tab control timeoutMs error7 people
Show all 35Show only the largest 10
  1. Browser unavailable to assistant4 people
  2. Embedded browser unusable when sidebar keeps client-new-thread conversation ID5 people
  3. Browser tab access lost5 people
  4. In-app browser not available4 people
  5. Browser service module missing3 people
  6. In-app browser policy check fails2 people
  7. Browser tools missing in chat4 people
  8. Chrome connection drops2 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 reports2, newest first

  1. Desktop browser use: browser IDs change on reconnect and break bindings that the docs say to reuseOn GitHub#59144
  2. macOS Chrome CUA: retained browser IDs become unavailable across calls while the extension and tab remainOn GitHub#53700

Do you work on Codex?

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