codex - 💡(How to fix) Fix sandbox profile bug

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…
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.513.20950 (2816)

What subscription do you have?

plus

What platform is your computer?

macos apple silicon

What issue are you seeing?

The Codex app does not apply the custom sandbox rules from config.toml, whether you choose [Default Permissions] or [Custom config.toml] in the UI...

What steps can reproduce the bug?

Codex App 0.131.0-alpha.9 ~/.codex/config.toml: default_permissions = "custom" [permissions.custom.filesystem] ":root" = "read" "/Applications/" = "none"

CLI: codex sandbox macos --permissions-profile custom -- ls -l /Applications/ => Operation not permitted

Codex App new thread: execute ls -l /Applications/ => succeeds

state_5.sqlite threads.sandbox_policy shows {"type":"read-only"} instead of custom PermissionProfile.

What is the expected behavior?

Codex apps should respect config.toml

Additional information

No response

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