Desktop task rejects GitHub branch-protection command; owner reports /approve unavailable

An owner-authorized GitHub branch-protection configuration command was rejected before process launch with:

“blocked by policy”

The enforcing component and specific rule were not exposed. The owner reported that the documented /approve command was not offered in the affected desktop task.

Feedback/session ID:
01a07e85-87e6-7d81-b524-9b04d0b7f2d0

Observed sequence:

1. An earlier request reached GitHub and returned HTTP 422 because its payload included both contexts and checks.
2. Read-back confirmed that no branch protection was created.
3. A corrected payload was prepared, removing only contexts and preserving the approved protection controls.
4. The execution tool rejected the corrected submission before process launch with “blocked by policy.” The enforcing component and specific rule were not exposed.
5. Feedback was submitted successfully, but no support case or response channel was supplied.
6. The owner reported that /approve was not offered in this task. No app-issued retry approval was established, and no further submission occurred.

Environment:

• Codex Local desktop task on Windows.
• Exact installed app/bundled Codex version: not established in this report.
• This describes an observed task failure; a standalone reproduction has not been executed.

Requested assistance:
Please identify the enforcing policy component and the supported retry-approval procedure for this task. If the operation is intentionally restricted, please explain the restriction and supported next step. Please clarify the availability requirements for /approve.

The GitHub payload error and the subsequent execution-policy rejection are separate events. No policy settings were weakened or alternative execution route used.

Documentation:
https://learn.chatgpt.com/docs/reference/slash-commands
https://learn.chatgpt.com/docs/reference/troubleshooting#feedback-and-logs

Start by confirming the exact installed Codex Local desktop version on Windows and reviewing the linked slash-command and feedback/troubleshooting documentation. Use feedback/session ID 01a07e85-87e6-7d81-b524-9b04d0b7f2d0 to investigate the policy rejection separately from the earlier GitHub HTTP 422. Done means identifying the enforcing component, documenting the supported retry-approval procedure, and clarifying when /approve is available.