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