Any filesystem deny rule prevents exiting the sandbox after approval
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start with codex-rs/core/src/tools/sandboxing.rs around lines 250-307 and reproduce the issue using a permissions profile with a deny rule, then approve escalation for access to that path. Trace how the deny rule affects the transition out of the sandbox. Done means escalation behaves as intended and the behavior is covered by a regression check.
Written by the indexing model from the issue text.
Description
What issue are you seeing?
When the current permission profile contains any deny rule, codex will not exit the sandbox after asking for approval. This makes escalation basically useless.
This is not documented at https://learn.chatgpt.com/docs/permissions
What steps can reproduce the bug?
- Use some profile of the new permissions that uses
denyon some paths - Tell codex to access that path, e.g. with
ls - Approve escalation to run out of sandbox
What is the expected behavior?
Deny rules should not be so special cased.
If the behaviour "deny always, even after escalation" is required, maybe:
- add a new keyword
- allow specifying which profile codex can escalate TO, so that even the escalated profile could still deny some paths.
Additional information
https://github.com/openai/codex/blob/rust-v0.144.2/codex-rs/core/src/tools/sandboxing.rs#L250-L307
- 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 ·