Codex Desktop ignores Full Access config and launches fresh tasks with CODEX_SANDBOX_NETWORK_DISABLED=1
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.825.51511
What subscription do you have?
pro/premium set
What platform is your computer?
No response
What issue are you seeing?
Summary
On macOS, Codex Desktop is configured for Full access, but every fresh Codex task is still launched under Seatbelt with outbound network explicitly disabled.
The host Mac has working DNS and GitHub access. The failure exists only inside Codex.
Environment
- macOS: 26.5.2
- ChatGPT / Codex Desktop app: 26.825.51511
- App build: 7377
- Codex Workspace bundle: 26.826.12353
- Project path:
/Users/bryanfleck/Documents/Codex/Cardwoven-clean
Configuration
The Codex Configuration UI shows:
- Approval policy: Never ask for approval
- Sandbox settings: Full access
- Web search: Live
~/.codex/config.toml contains:
approval_policy = "never"
sandbox_mode = "danger-full-access"
### What steps can reproduce the bug?
Feedback ID: no-active-thread-01a054e2-3a70-7740-8f03-478a905e79c8
### What is the expected behavior?
_No response_
### Additional information
_No response_
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.
Research direction
Start with the reported ~/.codex/config.toml settings and the fresh-task launch path, using Feedback ID no-active-thread-01a054e2-3a70-7740-8f03-478a905e79c8 as context. Reproduce on macOS with Full access enabled and verify that a new task no longer launches with CODEX_SANDBOX_NETWORK_DISABLED=1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100