Rank, 14 days: 14 on the Codex sheet
58 people reported

All time, since Sep 14, including 10 thumbs-up on GitHub.

Unexplained blocked by policy

“An owner-authorized, guarded read-only verification launcher was rejected before process creation in Codex desktop.”

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

Fading. 6 reports and thumbs-up in the last 7 days and 10 the week before, down from 12 a week at the mid-October peak.

Commands rejected as blocked by policy with no reason given. In Windows desktop, user-authorized exec_command calls are rejected before process creation under approval_policy never and danger-full-access, with no enforcing rule identified.

Is this your bug?

File my report
Where
Windows desktop app
Error text
exec_command failed: CreateProcess ... Rejected(... rejected: blocked by policy)
Versions
0.153.4 to 26.1016.62342
Platforms
Windows
How bad
Breaks a normal workflow. Some reports say it blocks them completely.

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

  1. Blocked by policy, no rule shown3 people
  2. Opaque blocked by policy rejection3 people
  3. PowerShell commands rejected when a URL and start appear together3 people

Not quite your bug?

  1. Server start blocked by policy2 people

Original reports49, newest first

  1. Windows: command rejected as “blocked by policy” despite Full access, with no actionable decision traceOn GitHub#59415
  2. Automatic approval review blocks approved read-only local Docker diagnostic without explanationOn GitHub#59216
  3. Windows desktop: local validation rejected before process creation; no /approve denial listOn GitHub#59023
  4. exec_command rejected by policy with Full access enabled and no approval or resume optionOn GitHub#58900
  5. VS Code on Windows: pre-execution blocked by policy with no matching execpolicy rule; feedback permission errorOn GitHub#58601
  6. Windows: Local CreateProcess command blocked by policy without explanationOn GitHub#58550
  7. approval_policy: NeverOn GitHub#58458
  8. Windows desktop: CreateProcess blocked by policy without actionable per-call denial detailsOn GitHub#58437
  9. Windows desktop: selected exec_command operations rejected before process creation with unexplained blocked by policyOn GitHub#58377
  10. [Windows desktop] exec_command rejected before process creation with only "blocked by policy"On GitHub#58234
Show all 49Show only the newest 10
  1. Windows Codex returns “blocked by policy” without an actionable reasonOn GitHub#57623
  2. Windows desktop: source-generation command rejected as “blocked by policy” without explanationOn GitHub#57566
  3. Windows desktop: authorized local video launch rejected before CreateProcess without an actionable policy reasonOn GitHub#56872
  4. Windows: unexplained “blocked by policy” refusal prevents safe editing-service recoveryOn GitHub#56867
  5. Codex on Windows rejects an authorised command with “blocked by policy” but gives no reason or recovery actionOn GitHub#56722
  6. Windows desktop: explicitly authorized directory deletion blocked by policy with Full Access and auto approve (26.1016.62342)On GitHub#56572
  7. Windows: opaque policy rejection blocks SHA-256-verified duplicate extraction cleanupOn GitHub#56344
  8. Windows: command rejected by policy under Full Access, no reason or matching approvalOn GitHub#56251
  9. Windows desktop: CreateProcess policy rejection gives no enforcing rule or supported authorization path (bundled CLI 0.163.0-alpha.10.2)On GitHub#55914
  10. Windows Full access blocks authorized file cleanup without an approval path; use Auto-review or restore previous behaviorOn GitHub#55197
  11. Windows: exec_command blocked before CreateProcess while creating three JSON filesOn GitHub#55022
  12. Codex Windows: CreateProcess Rejected blocked by policy despite Full AccessOn GitHub#54746
  13. Windows: unexplained "blocked by policy" prevents test-artifact cleanup despite effective Full AccessOn GitHub#54610
  14. CreateProcess Rejected: blocked by policy — request per-call investigationOn GitHub#54206
  15. Windows Codex app 26.1007.71326, build 20398. An explicitly authorized Test-only deployment coordination command is rejectedOn GitHub#54126
  16. Windows: authorised local commands rejected with “blocked by policy” and no explanationOn GitHub#53982
  17. Windows IDE extension: exec_command fails with “CreateProcess … rejected: blocked by policy” without an actionable explanationOn GitHub#53981
  18. Windows desktop: pre-launch CreateProcess policy denial with full-access turn context and no actionable reasonOn GitHub#53979
  19. Windows Codex desktop: read-only local diagnostic command rejected with CreateProcess: blocked by policyOn GitHub#53977
  20. Desktop: local recorder preflight evidence command rejected before execution with only “blocked by policy”On GitHub#53948
  21. Windows app: “blocked by policy” with Full Access and unconfirmed feedback submissionOn GitHub#53215
  22. Codex Windows pre-execution policy rejection blocking owner-authorized local gateway recoveryOn GitHub#52914
  23. Windows desktop: local preview replacement rejected before process creation with no actionable policy reasonOn GitHub#52202
  24. Windows: authorized cache cleanup blocked, followed by repeated stale refusals without fresh execution attemptsOn GitHub#52170
  25. [ChatGPT → Codex][Remote MCP] Opaque safety block propagates into repeated refusal without native approval or recoveryOn GitHub#52095
  26. Windows Desktop: authorized local app/gateway update blocked by policy and misreported as auto-review denialOn GitHub#52019
  27. errorOn GitHub#51418
  28. Windows: authorized cleanup and read-only command-text diagnostic rejected before executionOn GitHub#50896
  29. Windows: exec_command rejected as “blocked by policy” without an actionable explanationOn GitHub#50884
  30. Windows Desktop pre-execution policy rejection has no rationale or verified review routeOn GitHub#50745
  31. Windows desktop blocks authorized service restart without an actionable explanationOn GitHub#50712
  32. Windows desktop: explicitly authorized duplicate-file cleanup rejected with "blocked by policy" and no actionable diagnosticOn GitHub#50565
  33. Unclear reason for rejection with “blocked by policy”; /approve shows no entriesOn GitHub#50524
  34. Windows: exec_command rejected with “blocked by policy” without an actionable explanationOn GitHub#49373
  35. Windows CLI 0.157.0: authorized local recovery blocked by policy without explanationOn GitHub#48202
  36. Windows IDE: local observer launch rejected as “blocked by policy” without an actionable approval recordOn GitHub#48128
  37. Full Access blocks commands without an approval prompt on WindowsOn GitHub#47213
  38. Windows: local Markdown QA report write rejected before execution with "blocked by policy", no review entryOn GitHub#45986
  39. Windows desktop Full access: forced test-file cleanup denied with opaque blocked by policy and no review pathOn GitHub#45403

Do you work on Codex?

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