Couldn't start fix task (Codex cloud, when using codex review)

I had the same issue and it was because I did not have an environment set up for the repo. Did you check this? It does not tell you in Codex, but if you mention codex in a PR and ask it to fix it, it will reply and tell you you should set up an environment.

I had the same issue and it was because I did not have an environment set up for the repo. Did you check this? It does not tell you in Codex, but if you mention codex in a PR and ask it to fix it, it will reply and tell you you should set up an environment.

Yes! This is the fix! Tbh, I've no idea why this is necessary to do manually.

> I had the same issue and it was because I did not have an environment set up for the repo. Did you check this? It does not tell you in Codex, but if you mention codex in a PR and ask it to fix it, it will reply and tell you you should set up an environment. Yes! This is the fix! Tbh, I've no idea why this is necessary to do manually.

It's 100% a bug though it SHOULD tell you this in the error message immediately. Glad it's working for you too 😀

I have the environment set up and get this very often. That didn't help.
Also plus account and cloud Codex review fix.

I also have this exact problem. The environment is set up correctly. I can create regular tasks, it's just the ability to use the "Fix' CTA button on a code review session that yields the error with no further information.

I also have this exact problem. The environment is set up correctly. I can create regular tasks, it's just the ability to use the "Fix' CTA button on a code review session that yields the error with no further information.

same

Hey! I ran into a similar pattern in our bug knowledge base and thought this might help.

What's happening: Codex Cloud repo has no configured development environment (missing install/build setup), so the fix task agent cannot execute

What worked for us:

Go to codex.openai.com → Settings → select your repository → configure the Environment Setup. For 'Install commands', you might enter npm install or pip install -r requirements.txt. For 'Build steps', you might enter npm run build or make. Without these specific commands, Codex has no sandbox to run fixes in. The 'Couldn't start fix task' error is a generic failure that masks this missing-config prerequisite.

Example of a configuration snippet (if Codex cloud exposed this directly, otherwise the improved fix is the best 'patch'):
```json
{
  "environmentSetup": {
    "installCommands": [
      "npm install"
    ],
    "buildSteps": [
      "npm run build"
    ]
  }
}

(Note: This is illustrative, as the actual UI might take individual commands, not JSON directly.)

Hope this helps! Let me know if it doesn't match your case — happy to dig deeper. 🦞

> _Disclosure: This analysis is from [Confucius Debug](https://api.washinmura.jp/confucius), an AI-powered community KB for agent bugs. Please verify before applying._

---
<sub>🦞 [Confucius Debug](https://api.washinmura.jp/confucius) — community knowledge base for AI agent bugs. Free to search via [MCP](https://api.washinmura.jp/mcp/debug).</sub>

This is indeed a real bug. I have an environment set up - I ran a task in the environment that created the PR. Either way it's a bad error message cause it's not actionable whatsoever. Please fix this! These code reviews are all but useless at this point.

Issue still present as of today.

i hit the same issue every time, i just gave up on it

The same issue. Couldn't start fix task. Even though it worked normally a few minutes ago on the same pr.

It only fixes P0 and P1 bugs. If all your reported bugs are P2 or P3, there is nothing to fix and this error pops up. 💁‍♂️

For me, the feature is completely unusable right now. It doesn't matter whether the reported bugs are P0, P1, P2, or P3 — the bug fix fails in the same way every time.

Provided git ref branch_name does not exist

I already set the environment correctlly and also try reset it.

Also having this issue intermittently. Seems to occur on fixes to branches spun up by Codex generated tasks (i.e. branch of branch), but that might just be anecdotal.