Codex CLI 0.154.0: HTTP 400 unsupported_parameter for access_programs.cyber

What version of Codex CLI is running?

Codex CLI 0.154.0: HTTP 400 unsupported_parameter for access_programs.cyber

What subscription do you have?

ChatGPT Business

Which model were you using?

gpt-6-astra, reasoning low, Fast mode enabled

What platform is your computer?

Ubuntu 26.04 LTS running in WSL2 on Windows. Linux kernel: 6.18.33.2-microsoft-standard-WSL2

What terminal emulator and version are you using (if applicable)?

Windows Terminal with an Ubuntu WSL2 shell. Terminal version not collected.

Codex doctor report

Not collected. I can provide a reviewed and redacted diagnostic report if needed.

What issue are you seeing?

Codex CLI repeatedly stops with HTTP 400 while preparing a local test package.

Error:
{
"type": "error",
"error": {
"type": "invalid_request_error",
"code": "unsupported_parameter",
"message": "The access_programs parameter is not enabled for this organization.",
"param": "access_programs.cyber"
},
"status": 400
}

Environment:

• Codex CLI 0.154.0
• ChatGPT Business
• Model: gpt-6-astra
• Reasoning: low
• Fast mode enabled
• Ubuntu on WSL2, using Windows Terminal

After the first failure, I asked Codex to resume from the existing files without running tests or changing access settings. It performed a local inspection, displayed "Context compacted", and then returned the same error.

I do not know whether compaction is related to the failure.

/status shows:

• 73% context remaining
• 5-hour limit: 100% remaining
• Weekly limit: 0% remaining
• Credits: Available

Expected behavior:
Codex should continue using the account's authorized capabilities, or provide an actionable explanation if an account limit prevents continuation.

Actual behavior:
The request fails with an unsupported_parameter error, leaving the preparation unfinished.

Feedback was recorded through /feedback without uploading session logs. Please investigate why access_programs.cyber is being sent and rejected.

What steps can reproduce the bug?

Uploaded thread: 01a09e86-deee-7ec3-8de0-78964769b560

What is the expected behavior?

Codex should continue the task using capabilities authorized for the account.

If an account limit or unavailable capability prevents continuation, it should provide an actionable explanation rather than repeatedly failing with an unsupported_parameter error.

Additional information

The “Steps to reproduce” field keeps reverting to the prefilled “Uploaded thread” text after editing. Reproduction steps are therefore included below.

Despite that prefilled wording, I declined session log upload. The CLI confirmed “Feedback recorded (no logs).”

Observed sequence in the affected session:

1. Use Codex CLI 0.154.0 with ChatGPT Business, gpt-6-astra, reasoning low, and Fast mode enabled, on Ubuntu under WSL2.
2. Ask Codex to prepare a local automated test package without executing the tests.
3. Codex performs local file operations, then stops with HTTP 400, unsupported_parameter, param access_programs.cyber.
4. Ask it to resume from existing files without changing access settings.
5. Codex performs another local inspection, displays "Context compacted", and returns the same error.

This happened repeatedly in the same session. I have not established a minimal reproduction or tested whether a new session reproduces it.

Feedback was recorded via /feedback with log upload declined.

/status showed 73% context remaining, 100% of the 5-hour limit remaining, 0% of the weekly limit remaining, and Credits: Available.

It is unclear whether the weekly limit or context compaction is related to this error.

The task remains unfinished. Some preparation files were saved before the interruption. No session logs or private project files are attached.

Start by reproducing the reported sequence with Codex CLI 0.154.0 on the stated ChatGPT Business and WSL2 setup, then trace where the request containing access_programs.cyber is assembled. Compare behavior with and without resuming or context compaction; done means the unsupported parameter is no longer repeatedly rejected or the CLI gives an actionable account-limit explanation.