#Why is GPT Codex 5.4 taking so long
1 messages · Page 1 of 1 (latest)
Yeah, 5 hours is not normal. If it keeps saying “still in progress” on simple tasks, something is probably off.
First thing I’d check:
-
openclaw --version
Older builds had more GPT-5.4/Codex “plans forever instead of acting” behavior. If you’re not on latest, update first. -
/model status
Make sure you know which route you’re on:openai-codex/gpt-5.4= Codex OAuth pathcodex/gpt-5.4= native Codex harnessopenai/gpt-5.4= direct OpenAI API
They behave differently.
-
Try these quick checks:
/fast on/thinkand make sure you didn’t leave it on a high thinking level
/newto test whether it’s just a bloated session/context issue
- Run the debug ladder:
openclaw status openclaw models status openclaw doctor openclaw logs --follow
Two especially relevant things from docs:
openclaw doctorcan catch stalemodels.providers.openai-codexoverrides that shadow the built-in Codex route.- If you’re using
codex/*, run/codex statustoo, and make sure the Codex app-server is healthy/current.
Docs:
- FAQ: https://docs.openclaw.ai/help/faq
- Troubleshooting: https://docs.openclaw.ai/help/troubleshooting
- Model providers: https://docs.openclaw.ai/concepts/model-providers
- Codex harness: https://docs.openclaw.ai/plugins/codex-harness
- Fast mode: https://docs.openclaw.ai/providers/openai
If you paste:
openclaw --version/model statusopenclaw models status- and a short
openclaw logs --followsnippet while one of these “stuck” runs is happening
…I can probably narrow it down pretty fast.
whats the default/recommended "think" mode option?
Short answer: for most setups, low is the sane default.
A good rule of thumb:
/think low= recommended starting point/think off= best if you want speed / less “chewing”/think mediumorhigh= only for genuinely tricky stuff
For your earlier Codex slowness complaint, I’d actually try:
/think low/fast on
If it’s still dragging on simple tasks, try /think off.
A couple of details from docs: