3 people reported

All time, since Sep 15.

PowerShell commands rejected when a URL and start appear together

“Windows command-safety treats a PowerShell parameter value as a URL launcher”

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

Quiet. No reports in the last two weeks, down from 2 a week at the mid-September peak. A workaround is known.

Windows URL-launch check matches a URL argument plus a separate "start" token or Start-Process, rejecting before PowerShell runs.

Is this your bug?

Where: Windows PowerShell commands
Error text: rejected: blocked by policy
Versions: 0.154.0 to 0.162.0
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Windows opaque blocked-by-policy rejections4 bugs

Unexplained blocked by policy58 people
Blocked by policy, no rule shown3 people
Opaque blocked by policy rejection3 people

Not quite your bug?

Server start blocked by policy2 people

Original reports3, newest first

Oct 18, 2026Windows: URL-launch classifier mistakes -Stage Start argument for a command under neverOn GitHub#55117
Sep 18, 2026[Windows App 26.908.9136.0] Guarded local API restart blocked before execution; possible cross-command URL-launch matchOn GitHub#46364
Sep 15, 2026Windows PowerShell execpolicy blocks benign CLI start subcommand with --server URLOn GitHub#45793

Do you work on Codex?

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