apply_patch bug
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- powershell
- Domain
- devtools, operating-systems
Research direction
Start with the apply_patch path and the Windows sandbox-wrapper behavior described in the report, comparing it with the successful direct PowerShell editing and CLI behavior. Reproduce the intermittent failure if possible; done means apply_patch can create and then update files reliably in the official and beta apps.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.715.31251
What subscription do you have?
Pro
What platform is your computer?
No response
What issue are you seeing?
Keep getting this it happens when i ask it to test out every command because ill be making edits and it will bug out and tell me apply_patch failed asked 5.6 to run a test:
Sandbox CRUD smoke test results:
Create directory: passed
Create file: passed
Read file: passed
Edit via PowerShell: passed
Delete file: passed
Delete directory: passed
Cleanup verification: passed; no test artifacts remain
One issue: apply_patch created the file successfully but failed when updating it due to a Windows sandbox-wrapper error. Direct sandboxed PowerShell editing worked normally.
What steps can reproduce the bug?
No idea its so random sometimes if i restart my computer (rarely) it will reactivate and work for a bit then break again.
What is the expected behavior?
No issues with apply_patch
Additional information
I've tried with both the official version/beta version both have the same issue if i use the CLI i have no issues at all i mainly use t3code to use my subscription right now and its kinda frustrating that the official tools aren't working
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·