gpt-5.4-pro is currently not usable in OpenCode through the OpenAI -> ChatGPT Plus/Pro OAuth/Codex flow, even if you have a ChatGPT Personal Pro subscription.
This note is meant to help people searching for phrases like gpt-5.4-pro not showing in OpenCode, ChatGPT Personal Pro OpenCode, gpt-5.4-pro Codex, and The 'gpt-5.4-pro' model is not supported when using Codex with a ChatGPT account.
- Confirmed that OpenCode hides
gpt-5.4-proin the OAuth/Codex model allowlist. - Applied a minimal local patch so the model appears in
opencode models openai. - Added a focused test for the allowlist behavior.
- Verified the patched build with typecheck and a smoke test.
- Ran real requests using an existing local ChatGPT OAuth login.
gpt-5.4works through the ChatGPT OAuth path.gpt-5.4-probecomes visible after the local patch, but the real request is rejected by the OpenAI backend.
Backend error:
The 'gpt-5.4-pro' model is not supported when using Codex with a ChatGPT account.
This is not only an OpenCode UI/filtering issue.
Even if OpenCode is patched to show the model, the OpenAI backend currently blocks gpt-5.4-pro for the ChatGPT account + Codex flow.
So for now:
ChatGPT Personal Pro + OpenCode OAuth->gpt-5.4-prodoes not work.gpt-5.4through the same flow does work.
OpenCode Zen is a separate provider/gateway with its own endpoint and billing flow.
It does not reuse your ChatGPT Personal Pro subscription. It exposes gpt-5.4-pro through Zen's own paid provider path, which is why the model may be available there even when it is blocked for ChatGPT OAuth/Codex.
If someone wants gpt-5.4-pro inside OpenCode, there is currently no clean workaround using only ChatGPT Personal Pro through the OpenAI OAuth/Codex integration.
The fix would need to come from OpenAI enabling that model for the ChatGPT-account Codex path, not just from OpenCode changing the local allowlist.