GPT‑5.5‑Cyber Codex entitlement mismatch after approval

What version of Codex CLI is running?

CLI 0.146.0

What subscription do you have?

pro

Which model were you using?

gpt-5.5-cyber-preview

What platform is your computer?

Linux 6.16.12-valve24.5-1-neptune-616-gb2f7cfe85e45 x86_64 unknown

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

konsole

Codex doctor report

■ {"type":"error","status":400,"error":{"type":"invalid_request_error","message":"The 'gpt-5.5-cyber-preview' model is not supported when using Codex with a ChatGPT account."}}

What issue are you seeing?

My Trusted Access for Cyber status is verified and approved. I am using Codex CLI 0.146.0 and authenticating through Sign in with ChatGPT.

GPT‑5.5‑Cyber‑Preview appears in the Codex model selector, and /status reports gpt-5.5-cyber-preview as the active model. However, every actual request immediately returns:

{"type":"error","status":400,"error":{"type":"invalid_request_error","message":"The 'gpt-5.5-cyber-preview' model is not supported when using Codex with a ChatGPT account."}}

Please confirm all of the following:

My specific ChatGPT user account is approved for GPT‑5.5‑Cyber, not only general Trusted Access for Cyber.
The entitlement is provisioned for Codex using Sign in with ChatGPT, not only the Responses API.
The entitlement is attached to the correct user and workspace.
User provisioning and backend organization enablement are complete.
My model-catalog visibility and backend execution entitlement are synchronized.

Codex feedback/session ID: 019fc765-fb15-71b2-830e-b384465342a3CLI version: 0.146.0

Authentication: Logged in using ChatGPT

Account plan: Pro

The work concerns defensive review of repositories and systems I own and am authorized to analyze.

What steps can reproduce the bug?

Uploaded thread: 019fc765-fb15-71b2-830e-b384465342a3

What is the expected behavior?

model-catalog/entitlement synchronization defect

Additional information

_No response_