Update, after swapping to Opera, I eventually ran into the same issue. I was working out of a sterile repo i made for a project, was still not able to use codex in it, deleted the repo and remade it, no issues now it will code away. Unsure if user error here but i have not had this issue before.
I am experiencing the same issue in latest release build of Chrome. I have two repos connected to Codex with one working without issue but the newest one connected is tossing errors, even if asked to verify why language of code is in the repo (C#). Tried in both Edge, Chrome and FireFox with no solutions. Deleted the repo causing issues and reconnected it, cleared cache/cookies, flushed the IP (just for coverage), but nothing fixes it.
So I think I see the error after some digging and troubleshoot, at least from my perspective. If the repo doesnāt have at least 1 commit on it, the system is failing it because my guess the repo has not been initialized. So if you are trying to have it build something from scratch, it fails out. If you perform a single commit, like readme.md, it works after this.
Again, this worked for me but others may be getting hit a different way.
4 Likes
Thanks for coming back to let us know! Hope it helps someone else in the future.
Hope you stick around. Weāve got a great community growing here! 
A post was split to a new topic: Is it possible to revert to the previous workflow, where Codex would generate a PR?
For me problem was empty repo without a README and initial commit. It was already mentioned in this thread, but Iāll do it again to draw more attention to this solution
This solution worked for me. Thanks a lot!
Just create a README file in the repo and Codex starts to work.
1 Like
Just create a README file in the repo and Codex starts to work. worked for me also
Itās been a while since someone posted to this thread, but since I just experienced a āFailed to create follow-upā error as well for the past hour or so, I thought Iād add to the collection here. In my case the problem only seems to exist in Firefox, at least for the time being. In Chrome, Codex seems to have started to work on the task now. This isnāt happening in a new nor empty repo but in one I had been working in for a while without problems, primarily with Firefox.
Edit: One day later - it works again in Firefox.
Hey @juliahaunschild, yeah thatās frustrating, especially if it was working fine before.
Youāre right that earlier in this thread a few cases were caused by empty repos with no initial commit. Since yours isnāt new or empty and Chrome works, this does sound more browser specific.
A couple quick things to try in Firefox:
ā¢ Hard refresh the page
ā¢ Open in a private window with no extensions
ā¢ Temporarily disable extensions
ā¢ Check the browser console for any red errors
If youāre still seeing this, can you also share your Firefox version, OS, and roughly when this started with timezone? That helps us see if it lines up with anything on our side.
If others are seeing this in Firefox too, definitely chime in. Thatāll help us narrow down whether itās isolated or broader.
1 Like