›_ Codex Issues
Codex Issues / #5098

More Apply Patch Bugs | Flavor: Sanity

Resolved 💬 2 comments Opened Oct 11, 2025 by Alfredo-Sandoval Closed Nov 12, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

_No response_

Which model were you using?

_No response_

What platform is your computer?

_No response_

What steps can reproduce the bug?

Use Codex.

What is the expected behavior?

Apply patches.

What do you see instead?

<img width="717" height="203" alt="Image" src="https://github.com/user-attachments/assets/d5dd90db-dc83-4f91-8a8a-f4622405a8ac" />

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #3858
  • #4233
  • #4320
  • #4003
  • #3953

Powered by Codex Action

0xdevalias · 9 months ago

I'm not 100% sure of this; but is this actually an issue with apply_patch? Or is it more of an issue with the binary itself trying to run (or something within it) not being there anymore? The error message sounds like something was deleted; maybe due to a version upgrade or similar?

Copying the relevant error text out of the screenshot (may not be perfectly accurately copied as it uses OCR):

failed in sandbox:
thread 'main' panicked at linux-sandbox/src/linux_run_main.rs:53:5:
Failed to execup /usr/local/lib/node_modules/@openai/.codex-vdnmINeK/vendor/x86_64-
unknown- Linux-musl/codex/codex (deleted): No such file or directory (os error 2)
note: run with "RUST BACKTRACE=1" environment variable to display a backtrace