#Failed to apply patch to repo

1 messages · Page 1 of 1 (latest)

umbral thistle
#

Hey, so I've been using Codex for the past like two weeks or so, and yesterday I've encountered an error which happened multiple times in a row. I'm not sure if this is the correct place for this, but nobody replied in #codex-discussions and I don't have access to #1070006915414900886. Sorry if this is wrong here!

I'm working solo on a Unity C# project with a GitHub repo.

The first prompt went by fine (even if I don't like that Codex always makes up its own first prompt from the tasks), but once I added a follow-up prompt, I get the following (censored) error message:

Failed to apply patch to repo /workspace/RepoName. This can happen if the setup script and agent modify the same files.
Looking into the logs:


Configuring language runtimes...
Running auto setup...
Scanning repository (up to depth 3) for dependency configurations...
No known dependency configuration files found up to depth 3.

Running auto setup...
Scanning repository (up to depth 3) for dependency configurations...
No known dependency configuration files found up to depth 3.
+ git -C /workspace/RepoName remote add origin https://oauth2:<auth>@github.com/username/RepoName.git
+ git -C /workspace/RepoName fetch origin --no-tags <hash>
fatal: unable to access 'https://github.com/username/RepoName.git/': CONNECT tunnel failed, response 403```

What is the issue here? All the changes I've done happened locally on my machine, I didn't commit or even stash anything, for all Codex should see no changes in the files. Even reverting my changes didn't do anything.

Even starting a new chat about the same issue didn't yield any different results. It also failed after one prompt.

What happened here? Codex looked through my merge request later on no issue after I got what I needed using regular GPT-5 Thinking. Although it also only did it once and the follow-up commit didn't get any comment, so either it got stuck again or I truly fixed everything that time...
image.png
prisma sentinel
#

Try the following:

  1. Log out & back into ChatGPT
  2. Log our & back into Github (new API key or whatever)
  3. Try changing the URL (use ssh:// instead of https://, get rid of trailing .git, etc.)
  4. If this is a private repository you may have to provide an API key with permissions to access the repo
  5. Check if you created an API key with a 2 week expiration date
#

I'm leaning more towards the API key had an expiration date but it could be anything

umbral thistle
#

@prisma sentinel I can rule all of that out after trying all of that. It's still happening.