Rank, 14 days: 130 on the Codex sheet
6 people reported

All time, since Oct 11, including 4 thumbs-up on GitHub.

URL safety stop gives no reason

“This session has been stopped because Computer Use is not allowed on the current browser URL.”

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/11540/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 Computer Use stops session without returning the evaluated URL. After earlier successful page reads, a native Chrome call returns the URL-not-allowed stop with no URL, policy source, reason category, or recovery route.

Is this your bug?

File my report
Where
Chrome Computer Use
Error text
This session has been stopped because Computer Use is not allowed on the current browser URL.
Versions
26.6.2 to 26.1007.30912
Platforms
macOS
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Site-safety block ignores allow19 people
  2. Browser blocks allowed site50 people
  3. Allowed site still denied10 people

Original reports2, newest first

  1. Native Chrome Computer Use refuses a publisher workflow without returning the evaluated URLOn GitHub#54248
  2. Chrome Computer Use changes from successful page reads to URL safety stop with no actionable reasonOn GitHub#53154

Do you work on Codex?

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