codex - 💡(How to fix) Fix 0.124.0 breaks sandbox when default_permissions is present in the config [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19299Fetched 2026-04-24 10:39:01
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2closed ×1mentioned ×1

Code Example

bwrap: execvp /home/user/.npm-global/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl/codex/codex: No such file or directory

---

default_permissions = "workspace"

[permissions.workspace.filesystem]
":minimal" = "read"
":project_roots" = "write"
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.124.0

What subscription do you have?

plus

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.12.69 x86_64 x86_64

Linux 6.8.0-78-generic x86_64 x86_64

What terminal emulator and version are you using (if applicable)?

No response

What issue are you seeing?

<img width="846" height="372" alt="Image" src="https://github.com/user-attachments/assets/d8b7f4e5-5742-4cde-aaef-c78114846068" />

For search:

bwrap: execvp /home/user/.npm-global/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl/codex/codex: No such file or directory

What steps can reproduce the bug?

Place in the ~/.codex/config.toml

default_permissions = "workspace"

[permissions.workspace.filesystem]
":minimal" = "read"
":project_roots" = "write"

What is the expected behavior?

No response

Additional information

It is the same behaviour as https://github.com/openai/codex/issues/17367, but in 0.123.0 it works well

It seems that the since switching to bubblewrap, the codex sandbox has been having frequent issues with the permissions.

extent analysis

TL;DR

The issue is likely due to a permissions problem with the Codex sandbox after switching to bubblewrap, and reverting the permissions configuration or checking the file path might resolve the issue.

Guidance

  • Check the file path /home/user/.npm-global/lib/node_modules/@openai/codex/node_modules/@openai/codex-linux-x64/vendor/x86_64-unknown-linux-musl/codex/codex to ensure it exists and is correctly referenced.
  • Verify that the default_permissions and permissions.workspace.filesystem settings in ~/.codex/config.toml are correctly configured and compatible with the current version of Codex CLI.
  • Compare the permissions configuration with the previous version (0.123.0) that worked well to identify potential changes that might be causing the issue.
  • Consider reverting to the previous version or adjusting the permissions configuration to match the working setup.

Notes

The issue seems to be related to a change in the Codex sandbox permissions after switching to bubblewrap, and the provided error message suggests a file not found error. However, without more information about the expected behavior, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Revert the permissions configuration to a previous working setup or adjust it to match the requirements of the current version, as the issue seems to be related to a change in the permissions configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING