#{"detail":"The 'openai-codex/gpt-5.4-mini' model is not supported when using Codex with ChatGPT acc
1 messages · Page 1 of 1 (latest)
Yeah, this smells like the .26 cron/model change, not your cron schedule itself.
In 2026.4.26, cron model overrides are stricter: if a job explicitly asks for a model like openai-codex/gpt-5.4-mini, OpenClaw won’t silently fall back to another/default model anymore. That error means the Codex/ChatGPT account route is rejecting that model.
Quick workaround:
openclaw cron edit <jobId> --model openai-codex/gpt-5.5
If you specifically need mini, use the OpenAI API-key route instead:
openclaw cron edit <jobId> --model openai/gpt-5.4-mini
…but that needs OPENAI_API_KEY, not Codex/ChatGPT OAuth.
Can you paste these?
openclaw --version
openclaw models list --provider openai-codex
openclaw cron show <one-failing-jobId>
openclaw cron runs --id <one-failing-jobId> --limit 5
Docs: https://docs.openclaw.ai/automation/cron-jobs and https://docs.openclaw.ai/providers/openai
Used failing job ID: 2c72759b-e54a-43a2-bad6-73cbf1deaae3 (Polymarket Weather Scan)
$ openclaw --version
OpenClaw 2026.4.26 (be8c246)
$ openclaw cron show 2c72759b-e54a-43a2-bad6-73cbf1deaae3
id: 2c72759b-e54a-43a2-bad6-73cbf1deaae3
name: Polymarket Weather Scan
enabled: yes
schedule: every 4h
session: isolated
agent: -
model: openai-codex/gpt-5.4-mini
delivery: none -> discord:channel:1484517851527118949 (explicit)
next: in 3h
last: 32m ago
status: error
$ openclaw models list --provider openai-codex
Model Input Ctx Local Auth Tags
openai-codex/gpt-5.4 text 195k no yes default,configured
openai-codex/gpt-5.5 text 195k no yes configured
openai-codex/gpt-5.4-mini text 195k no yes configured
$ openclaw cron runs --id 2c72759b-e54a-43a2-bad6-73cbf1deaae3 --limit 5
1. status=error
error={"detail":"The 'openai-codex/gpt-5.4-mini' model is not supported when using Codex with a ChatGPT account."}
model=openai-codex/gpt-5.4-mini
provider=openai-codex
2. status=error
error=cron: job execution timed out
3. status=error
error=cron: job execution timed out
4. status=error
error=cron: job execution timed out
5. status=ok
summary=Posted.
Paper journal: 32 resolved | 8 open | 41.9% win rate | -$575.66 P&L.
126 markets scanned. 2 trades executed. 0 punts.
Open positions: 10.
That output confirms it pretty cleanly: the job is resolving the model locally, but the live Codex/ChatGPT backend rejects it at call time.
The confusing bit is this row:
openai-codex/gpt-5.4-mini ... yes configured
configured means OpenClaw has a local/configured model row for it — not that your ChatGPT/Codex account can actually run it right now. Then the actual run hits:
The 'openai-codex/gpt-5.4-mini' model is not supported when using Codex with a ChatGPT account.
So yes: for 2026.4.26, this is at least a regression in behavior/UX. Cron is now failing closed instead of silently falling back to a different model, which is intentional, but advertising openai-codex/gpt-5.4-mini as usable when upstream rejects it is ugly.
Immediate fix for that job:
openclaw cron edit 2c72759b-e54a-43a2-bad6-73cbf1deaae3 --model openai-codex/gpt-5.4
openclaw cron run 2c72759b-e54a-43a2-bad6-73cbf1deaae3
If you specifically need mini, switch that job to the direct OpenAI API route instead:
openclaw cron edit 2c72759b-e54a-43a2-bad6-73cbf1deaae3 --model openai/gpt-5.4-mini
…but that requires OpenAI API-key auth, not ChatGPT/Codex OAuth.
I’d file this as a GitHub issue with exactly the snippets you posted, especially the mismatch between models list and the runtime rejection: https://github.com/openclaw/openclaw/issues
File it yourself
I can’t file GitHub issues myself — I’m read-only for project ops. Annoying, I know.
Paste this:
Title: 2026.4.26: openai-codex/gpt-5.4-mini listed as available but cron fails with ChatGPT account unsupported
Body:
OpenClaw 2026.4.26 (be8c246)
After updating to .26, isolated cron jobs using `openai-codex/gpt-5.4-mini` started failing.
`openclaw models list --provider openai-codex` shows:
- openai-codex/gpt-5.4
- openai-codex/gpt-5.5
- openai-codex/gpt-5.4-mini
`gpt-5.4-mini` is shown as configured/authenticated, but the cron run fails with:
{"detail":"The 'openai-codex/gpt-5.4-mini' model is not supported when using Codex with a ChatGPT account."}
Example cron job:
- id: 2c72759b-e54a-43a2-bad6-73cbf1deaae3
- name: Polymarket Weather Scan
- session: isolated
- model: openai-codex/gpt-5.4-mini
Expected:
Either the model should work, or `models list` / cron validation should not present it as usable for Codex ChatGPT OAuth.