Codex Desktop sandbox stuck with CODEX_SANDBOX_NETWORK_DISABLED=1 despite host network working

Open 💬 1 comment Opened Jun 27, 2026 by diegominsoni

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

Last update

What subscription do you have?

Plus

What platform is your computer?

windows

What issue are you seeing?

Hi OpenAI support,

I’m using Codex Desktop on Windows with a local repo. In a previous turn I may have denied a network/access permission, and since then the Codex tool sandbox appears to be stuck without network access.

Evidence:
Inside Codex tool execution:

  • Get-ChildItem Env:CODEX_SANDBOX_NETWORK_DISABLED returns:

CODEX_SANDBOX_NETWORK_DISABLED=1

  • Test-NetConnection github.com -Port 443 -InformationLevel Quiet returns:

False

  • git push, git ls-remote, and Trello API calls fail from Codex with network errors.

However, outside the sandbox on the same Windows machine:

  • Test-NetConnection github.com -Port 443 -InformationLevel Quiet returns:

True

  • git push origin main works from normal PowerShell.
  • Trello API scripts work from normal PowerShell.

I checked Windows environment variables:

  • CODEX_SANDBOX_NETWORK_DISABLED is not set at User level.
  • It is not set at Machine level.
  • It only appears inside the Codex process.

Forking the chat/thread did not restore network access; the new fork still showed CODEX_SANDBOX_NETWORK_DISABLED=1.

Question:
How can I reset/re-enable network permissions for this Codex Desktop workspace/thread/sandbox? Is there a local permission cache or setting I can clear? Can you please provideme step-by-step resolution!

Environment:

  • OS: Windows
  • Shell: PowerShell
  • Repo path:

C:\Users\diego\Documents\Codex\2026-06-07\sos-el-agente-codex-trabajando-en\work\lf-management-webApp

  • Network works on host, fails only inside Codex tool sandbox.

Thanks.

What steps can reproduce the bug?

Feedback ID: 019f055d-be47-7752-a711-5d7a94e7e304

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗