Is creating new tasks in Codex the only way to update branches?

After creating a new task in Codex the sysem first clones the GitHub repo to its virtual machine. Later I tell it to create the PR on GitHub. Work is not done though and I have pushed an update to that new branch. Now I want Codex to pull my last changes from the GitHub repo to its virtual machine again. However, Codex tells me this:

Because there is no origin (or any other remote) defined, git pull or git fetch cannot contact a remote repository. Thus, no, you cannot pull from origin in this environment.
root@1907cc1bc448:/workspace/test# git remote -v
root@1907cc1bc448:/workspace/test#

So apparently the GitHub remote has been deleted by Codex. Probably for security reason, the same as it cannot access the internet after setting up the virtual machine.

But this seems to be a bug in the design of this security system. I understand that access to the Internet is not allowed, but updating (pulling) from the very same repo Codex has originally cloned from in the first place seems like a must have for collaboration with the system. Or are we supposed to create a whole new task in Codex and thus a new branch and PR on GitHub everytime after we had updated something Codex has created on GitHub?

We shipped a feature to update PRs! https://help.openai.com/en/articles/11428266-codex-changelog

3 Likes

That was fast, thank you!