All codex modules not supported apart from 5.4 | Friends of the Crustacean 🦞🤝 | Page 1

deep locust Apr 15, 2026, 10:55 AM

#

I have been working fine for some time, however starting recently i am unable to use any of the codex models apart from 5.4 with my agents. I get the error: {"detail":"The 'gpt-5.1' model is not supported when using Codex with a ChatGPT account."}

It doesnt matter if im using 5.1, 5.2, 5.3 or any variant, they all say the same thing (with the respective models in the error message).

Seems to be a lot of people reporting similar issues

#

@dim pike are you here?

dim pikeBOT Apr 15, 2026, 11:11 AM

#

Let me check the relevant OpenClaw docs/code paths, because this smells more like an upstream Codex entitlement/catalog restriction than your agent config.

#

Yep, I’m here 🦐

This looks real, not like you broke your config.

I checked the current docs/code:

ChatGPT/Codex sign-in goes through openai-codex/*
the docs currently only guarantee openai-codex/gpt-5.4 on that route
OpenClaw even has a fresh live test that treats your exact error (not supported when using Codex with a ChatGPT account) as a known upstream blocker

So my read is: this is very likely an OpenAI/Codex account restriction change, not an agent bug on your side.

Can you paste these 3 outputs so I can confirm which path you’re on?

openclaw --version
openclaw models status

#

openclaw models list --provider openai-codex

If you need the non-5.4 GPT variants specifically, the likely workaround is to use the direct OpenAI API route (openai/* with OPENAI_API_KEY) instead of ChatGPT/Codex OAuth.

Docs:

deep locust Apr 15, 2026, 11:20 AM

#

ubuntu@vps-23287a21:~$ openclaw --version
OpenClaw 2026.4.14 (323493f)

#

ubuntu@vps-23287a21:~$ openclaw models status

🦞 OpenClaw 2026.4.14 (323493f)
I speak fluent bash, mild sarcasm, and aggressive tab-completion energy.

Config : ~/.openclaw/openclaw.json
Agent dir : ~/.openclaw/agents/main/agent
Default : openai-codex/gpt-5.4
Fallbacks (2) : openai-codex/gpt-5.3-codex, openai-codex/gpt-5.2-codex
Image model : -
Image fallbacks (0): -
Aliases (0) : -
Configured models (1): openai-codex/gpt-5.4

Auth overview
Auth store : ~/.openclaw/agents/main/agent/auth-profiles.json
Shell env : off
Providers w/ OAuth/tokens (1): openai-codex (2)

openai effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | openai:default=sk-proj-...jDMWXM4A
openai-codex effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=2 (oauth=2, token=0, api_key=0) | openai-codex:default=OAuth, openai-codex:david@davidreidphotography.com=OAuth (david@davidreidphotography.com)
openrouter effective=profiles:~/.openclaw/agents/main/agent/auth-profiles.json | profiles=1 (oauth=0, token=0, api_key=1) | openrouter:default=sk-or-v1...5ccdae54

OAuth/token status
[openai-codex] Token refresh failed: 401 {
"error": {
"message": "Your refresh token has already been used to generate a new access token. Please try signing in again.",
"type": "invalid_request_error",
"param": null,
"code": "refresh_token_reused"
}
}

openai-codex usage: 5h 77% left ⏱2h 17m · Week 43% left ⏱1d 9h
- openai-codex:david@davidreidphotography.com (david@davidreidphotography.com) ok expires in 10d
- openai-codex:default ok expires in 0m
  ubuntu@vps-23287a21:~$

dim pikeBOT Apr 15, 2026, 11:20 AM

#

Nice, thanks, 2026.4.14 is recent, so this probably is not just an old OpenClaw build.

Can you paste these next?

openclaw models status
openclaw models list --provider openai-codex

If you’re using the Codex harness too, also this:

openclaw models list --provider codex

That’ll tell us whether:

OpenClaw is seeing those models at all, or

#

OpenAI is advertising/rejecting them account-side.

Relevant docs: https://docs.openclaw.ai/cli/models and https://docs.openclaw.ai/providers/openai

#

Two things jump out in that status output, so I’m checking the exact safe commands before I tell you to touch auth/fallbacks.

#

Ah, that helps a lot.

What your status says:

Your actual configured default is already openai-codex/gpt-5.4
The only other Codex models OpenClaw is set to try are fallbacks:
- openai-codex/gpt-5.3-codex
- openai-codex/gpt-5.2-codex
You also have a stale Codex OAuth profile:
- openai-codex:default is expired
- refresh is failing with refresh_token_reused

So my read is:

the 5.2/5.3 Codex fallbacks are now being rejected upstream for ChatGPT-backed Codex OAuth
and your stale default OAuth profile is worth cleaning up too

I’d do this next:

#

openclaw models fallbacks remove openai-codex/gpt-5.3-codex
openclaw models fallbacks remove openai-codex/gpt-5.2-codex
openclaw models auth login --provider openai-codex --set-default

Then verify with:

openclaw models status
openclaw models list --provider openai-codex

If you specifically want 5.2/5.3 class models, I’d use the direct OpenAI API route (openai/* with your API key) instead of ChatGPT/Codex OAuth.

Docs:

https://docs.openclaw.ai/cli/models

#

https://docs.openclaw.ai/providers/openai

If you paste the models list --provider openai-codex output after that, I can sanity check it.

deep locust Apr 15, 2026, 11:22 AM

#

ubuntu@vps-23287a21:~$ openclaw models list --provider openai-codex

🦞 OpenClaw 2026.4.14 (323493f) — Hot reload for config, cold sweat for deploys.

Model Input Ctx Local Auth Tags
openai-codex/gpt-5.4 text+image 1025k no yes default,configured
openai-codex/gpt-5.3-codex text+image 266k no yes fallback#1
openai-codex/gpt-5.2-codex text+image 266k no yes fallback#2
ubuntu@vps-23287a21:~$

dim pikeBOT Apr 15, 2026, 11:22 AM

#

Yep, that pretty much confirms it.

What that output shows is:

openai-codex/gpt-5.4 is your real/default Codex OAuth model
openai-codex/gpt-5.3-codex and openai-codex/gpt-5.2-codex are just your configured fallbacks
when OpenClaw tries those, OpenAI is rejecting them for ChatGPT-backed Codex auth

So the practical answer right now is: for openai-codex/*, 5.4 is the only safe one in your setup.

I’d clean it up like this:

openclaw models fallbacks remove openai-codex/gpt-5.3-codex
openclaw models fallbacks remove openai-codex/gpt-5.2-codex
openclaw models auth login --provider openai-codex --set-default

#

Then if any agent config explicitly pins openai-codex/gpt-5.2-codex or openai-codex/gpt-5.3-codex, switch those to openai-codex/gpt-5.4.

If you need 5.2/5.3 specifically, use the direct OpenAI API path (openai/* with OPENAI_API_KEY) instead of Codex OAuth.

If it still behaves weirdly after removing those fallbacks and re-authing, I’d call that issue-worthy and file it here: https://github.com/openclaw/openclaw/issues

If this fixes it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it.

deep locust Apr 15, 2026, 11:23 AM

#

so the only way to use openai-codex account is with the most expensive models? that makes it unusabe due to the rate limiting will just destroy all usage

dim pikeBOT Apr 15, 2026, 11:24 AM

#

Honestly, yeah, for ChatGPT/Codex OAuth, that’s what it looks like right now, and I agree, that’s frustrating.

Small nuance: on openai-codex/* you’re not paying normal API token pricing, but you are burning through OpenAI’s usage windows/quota. If only gpt-5.4 is allowed, the practical result is basically what you said, it becomes a bad fit fast.

My recommendation:

Do not use Codex OAuth as your default
Keep openai-codex/gpt-5.4 as a manual/special-case model
Use a different default for everyday agent turns
If you specifically want model choice like 5.2/5.3, use the direct OpenAI API route (openai/* with OPENAI_API_KEY) instead of ChatGPT/Codex OAuth

So, short version: Codex OAuth currently looks best treated as a limited premium lane, not a general default.

Docs:

#

And for freshest real-world reports on what OpenAI is allowing this week, check #models too. If you want, I can help you set up a sane “cheap default + Codex only when needed” config.

deep locust Apr 15, 2026, 11:43 AM

#

thats not really a solution unfortunately, how do we raise this up to the developers to resolve?

dim pikeBOT Apr 15, 2026, 11:43 AM

#

Yeah, I agree, that’s a workaround, not a fix.

For maintainer attention, the right path is a GitHub issue here:
https://github.com/openclaw/openclaw/issues

I’d include:

Version: OpenClaw 2026.4.14 (323493f)
Exact error:
{"detail":"The 'gpt-5.1' model is not supported when using Codex with a ChatGPT account."}
What changed: “Worked previously, started failing recently”
Repro: trying openai-codex/gpt-5.1/5.2/5.3 on a ChatGPT/Codex OAuth account, only openai-codex/gpt-5.4 works
Outputs:
- openclaw models status
- openclaw models list --provider openai-codex

Suggested title:

#

openai-codex gpt-5.1/5.2/5.3 rejected on ChatGPT/Codex OAuth, only gpt-5.4 works

If you want, I can help you draft the exact issue body before you post it.

deep locust Apr 15, 2026, 11:44 AM

#

yep please

dim pikeBOT Apr 15, 2026, 11:45 AM

#

Yep, use this, and redact your email/profile names if you want before posting:

Title

openai-codex gpt-5.1/5.2/5.3 rejected on ChatGPT/Codex OAuth, only gpt-5.4 works

Body

### Summary

Recently, OpenClaw stopped working for me with Codex models other than `openai-codex/gpt-5.4` when using a ChatGPT/Codex OAuth account.

`gpt-5.1`, `gpt-5.2`, and `gpt-5.3` variants all fail with:

```json
{"detail":"The 'gpt-5.1' model is not supported when using Codex with a ChatGPT account."}

#


(The model name in the error changes depending on which one I try.)

This worked previously, and it seems like other users are seeing similar behavior.

### Version

```text
OpenClaw 2026.4.14 (323493f)

Expected behavior

If these openai-codex/* models are still meant to work with ChatGPT/Codex OAuth, they should run successfully.

#

If OpenAI no longer supports them on ChatGPT-backed Codex auth, OpenClaw should probably stop surfacing/using them for that auth path, or at least give a clearer hint that only `openai-codex/gpt-5.4` is currently usable.

### Actual behavior

Only `openai-codex/gpt-5.4` works for me.

Other Codex models/variants fail with:
```json
{"detail":"The '<model>' model is not supported when using Codex with a ChatGPT account."}

Reproduction

Authenticate with openai-codex / ChatGPT-Codex OAuth
Try using a non-gpt-5.4 Codex model, for example a gpt-5.1, gpt-5.2, or gpt-5.3 variant

#

3. Observe the request fail with the unsupported-model error above

### `openclaw models status`

```text
🦞 OpenClaw 2026.4.14 (323493f)

Config : ~/.openclaw/openclaw.json
Agent dir : ~/.openclaw/agents/main/agent
Default : openai-codex/gpt-5.4
Fallbacks (2) : openai-codex/gpt-5.3-codex, openai-codex/gpt-5.2-codex
Configured models (1): openai-codex/gpt-5.4

Auth overview
Auth store : ~/.openclaw/agents/main/agent/auth-profiles.json
Shell env : off

#

Providers w/ OAuth/tokens (1): openai-codex (2)

OAuth/token status
[openai-codex] Token refresh failed: 401 {
"error": {
"message": "Your refresh token has already been used to generate a new access token. Please try signing in again.",
"type": "invalid_request_error",
"param": null,
"code": "refresh_token_reused"
}
}

openai-codex usage: 5h 77% left ⏱2h 17m · Week 43% left ⏱1d 9h


### `openclaw models list --provider openai-codex`

```text

#All codex modules not supported apart from 5.4

Expected behavior

Reproduction