Constant "Bad Request" happening to me
Resolved 💬 8 comments Opened Feb 1, 2026 by Monkopedia Closed Feb 4, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.93.0
What subscription do you have?
Pro
Which model were you using?
tried with all models
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
_No response_
What issue are you seeing?
Constant "Bad Request" happening
What steps can reproduce the bug?
Uploaded thread: 019c1983-b1af-72a1-99ae-ebf08ac45e36
What is the expected behavior?
_No response_
Additional information
_No response_
8 Comments
Based on the logs, I'm guessing that you've enabled a feature that is still under development and is not yet supported. Please review your config.toml.
Would background terminal be one of those?
Try renaming your
config.tomlfile temporarily, then relaunch Codex and log in. Do you still see the "Bad Request" in that case?Yes. 019c200d-be63-7152-aa8b-2b084f20432a
Sorry, I haven't been doing dev on the machine that was giving me these problems, will try again when I get a chance.
This is no longer reproducing for me, sorry.
I am currently having this all the time. Every second request gets me a red {"detail":"Bad Request"} even requests that are rather short and do not require lots of tokens (as it looks to me at least). I cannot let codex run unattended for more than a few minutes just to come back at it stopped mid-flight.
I am exclusively using codex 5.3 with xhigh thinking with my Pro account. I also told it to avoid parsing/sending large results but it happens at random times.
here is my config
@pardeike, when you see this happen, please use the
/feedbackcommand to upload your logs and session details, then post the thread ID here.Edit: Sorry, I just saw your post in #10571. Thanks for uploading your details.