Rank, 14 days: 103 on the Codex sheet
2 people reported

All time, since Nov 4.

Heartbeat browser not found

“A scheduled read-only monitoring heartbeat could not discover any browser.”

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

Heartbeat cannot find built-in browser until chat is shown. Scheduled heartbeat gets an empty browser list and 'Browser is not available: iab'; a later turn or showing the same chat works.

Is this your bug?

File my report
Where
In-app Browser
Error text
Browser is not available: iab
Platforms
Windows
How bad
Breaks a normal workflow.

Related: Browser control fails to connect

Not quite your bug?

  1. Embedded browser unusable when sidebar keeps client-new-thread conversation ID5 people
  2. Browser unavailable to assistant4 people
  3. Browser tools missing in chat4 people

Original reports2, newest first

  1. [Windows] Heartbeat browser discovery returns []; logs show missing session route before same-chat recoveryOn GitHub#60838
  2. [Windows] In-app Browser fails to bind during a background heartbeat and recovers when the chat is shownOn GitHub#59469

Do you work on Codex?

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