Codex Web gets stuck in read-only QA

Open 💬 1 comment Opened Mar 24, 2026 by etleli

What issue are you seeing?

I have noticed a few times in the past days, that if I'm working in a codex web task, that if i add the /plan comment to ask something about the code and then afterwards want to continue with coding, i get a text answer as if i would have used /plan (yes i removed it) and codex proposes to code this in a seperate task (which is also useless since for some reason its based on the base branch of the original codex task and not the new created one, which means the changes of the original codex task are missing)it also says that codex is now in read-only QA and no matter what i try, it stays in read-only for that task.

This all worked before.

What steps can reproduce the bug?

  • Go to codex web
  • Make a new task and change some code
  • Create a new PR
  • Use /plan and ask something about the code
  • Remove /plan and ask codex to change something in the code

What is the expected behavior?

Normally Codex switches back into coding mode after i removed /plan.

Additional information

I use the codex web enviroment in default mode, no custom script, no internet access, container caching on and universal container image.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗