9 people reported

All time, since Sep 18, including 7 thumbs-up on GitHub.

access_programs.cyber HTTP 400

“The specific failed outbound request and the component that added the parameter have not been identified.”

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

Requests fail HTTP 400 on unsupported access_programs.cyber parameter. Request fails with invalid_request_error saying "The access_programs parameter is not enabled for this organization" during local test package and maintenance work.

Is this your bug?

File my report
Where
Codex CLI
Error text
The access_programs parameter is not enabled for this organization.
"type": "error",Pasted in 2 reports
Versions
0.154.0
Platforms
Linux, Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. cyber_policy stops sessions2 people
  2. Cybersecurity notice hides responses23 people
  3. Cybersecurity safety check stops authorized defensive work on owned code10 people

Original reports2, newest first

  1. Codex CLI 0.154.0: HTTP 400 unsupported_parameter for access_programs.cyberOn GitHub#46481
  2. Unexpected access_programs.cyber parameter causes HTTP 400 during ordinary Codex workOn GitHub#46398

Do you work on Codex?

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