Refusal after blocked attempt

“It treated the rejection of one Remove-Item command shape as proof that the cleanup task itself was forbidden.”

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

Refuses authorized task via another tool after one block. After one command or tool was "blocked by policy", the model treats the same scoped task as forbidden and refuses to try an alternative.

Is this your bug?

File my report

Where: Agent tool use
Error text: exec_command failed: CreateProcess ... rejected: blocked by policy
Versions: 0.163.0
Platforms: Windows

Related: Windows opaque blocked-by-policy rejections

Not quite your bug?

Original reports2, newest first

Nov 10, 2026Switching tools after a blocked attempt triggers blanket refusal instead of reassessmentOn GitHub#60603
Oct 22, 2026GPT-6 Astra max turns one deletion-command rejection into a false permanent refusal loopOn GitHub#56086