Allow PRs with binary files

Same here, or at least, let us delete the binary and create PR. It is so annoying to loose all work due to this error.

same here.

I was just getting into Codex and then found out about this limitation. So frustrating! Does Claude Code have this problem? Might be a reason to switch.

yes this needs to be fixed please

It has been like this since launch - makes it not really usable for some workflows.

Workaround is .gitignore common binary files.

same here. it needs to be fixed i am having issues creating a PR!

Yeah it's impossible to e.g. create a bun lockfile (bun.lockb) or create a PR for a codex change that inclues such a change this way -- not sure I understand the intent here -- shouldnt you be able to "allowlist" such changes at least (e.g. bun.lockb files are ok to commit)?

Hit the same issue, I think it is pretty common use case and surprised that it is not fixed yet.

This is the same for me. You have to exclude everytime the binary files or find a workaround with those files ... It's literally painful.

Same for me - Gradle wrapper jar is automatically added to the build and cannot be committed to the repo.
Just add the possibility to exclude specific files from the PR to avoid messing up with workarounds.

Partial workaround is to use "copy git apply". The below post says to paste to a .patch file, then run git apply ThatFile.patch, but I think what's copied is the commands to run themselves, with data included.

https://community.openai.com/t/codex-started-failing-to-create-new-pr/1264529/40

I was recently able to create a PR with a binary bun lock file, so maybe this is fixed?

Just tried with a .png , still get binary files not supported error. Sad.

On Tue, 23 Dec 2025, 06:09 Thomas Grice, @.***> wrote:

z0d14c left a comment (openai/codex#4867) <https://github.com/openai/codex/issues/4867#issuecomment-3685270646> I was recently able to create a PR with a binary bun lock file, so maybe this is fixed? — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/4867#issuecomment-3685270646>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVKQFBCBIQ2M63RZUM3INT4DDMDNAVCNFSM6AAAAACIPJDCGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBVGI3TANRUGY> . You are receiving this because you commented.Message ID: @.***>

When this happens you can ask codex to remove the offending binary file and you will be able to create the PR without issues. Then you manually add the file in the PR itself if you need it.

G

My PR was about adding some QR codes to a website, it worked out and generated static images of the QR code (which is what I asked), but then it causes the same error when I try create the PR :/

Same here. One case is when you are asking CodeX to compile a binary from a repo with very complex environment & system requirements, and the compilation was finally successful, then the security mechanism blocks it. In this case we do expect PRs to include binaries.

I uploaded screenshots in the codex web UI and asked it to add them and update my README with them, but it fails at update-branch because "it doesn't support binary files"

Any updates on this issue? It should be at least possible to manually review binary files, or override this setting, or to be able to whitelist some types of files. Using codex to automate generating a readme file with images and getting blocked by this is very unfortunate.

As of 28 Jan 2026, this issue is still present. We expect at least an allowlist/whitelist within the project scope, i.e., shifting responsibility for potential risks to the user.

agreed, especially for users with business plans where we know the risk

This is still a problem in Feb 12 2026. I wasn't even aware it was an issue. I just ran the most ambitious project request I have ever tried with codex, and judging by the preview render, it did everything I asked for, and now I can't get at it. Super frustrating and my trust, already low, has plummeted.

Still a problem on February 17 :(
My first test with Codex wasn't pleasant because of this. It's a pity, all the rest looks great.

UP for prio

if we cant generate PRs with binary files at least limit the creation of said files

Partial workaround is to use "copy git apply". The below post says to paste to a .patch file, then run git apply ThatFile.patch, but I think what's copied is the commands to run themselves, with data included. community.openai.com/t/codex-started-failing-to-create-new-pr/1264529/40

This one worked for this. Thanks.

Still an issue 😭

Please fix this 🙏.

This really makes codex cloud useless. This should be high priority bug not an enhancement as this means I need to handle this locally.