A sandbox mode that restricts file access but allows free network access (with or without cached web searches)
Resolved 💬 5 comments Opened Mar 3, 2026 by jrd-1 Closed May 2, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
CLI
What feature would you like to see?
Running on Windows (haven't tried macos), unless the sandbox mode is "danger-full-access", network access seems to always be restricted. While this behaviour is great for many things, writing network components is incredibly challenging in this environment because connectivity often simply doesn't work (and you aren't asked for escalation in many cases). A sandbox mode with full network access while retaining the workspace file access restrictions would be a godsend. The option to use cached web searches would be beneficial in this case.
reported against codex cli 0.106.0.
Additional information
_No response_
5 Comments
Please refer to this documentation.
I followed the documentation, spent a few hours with it actually; it doesn't seem to be effective in resolving the network access restrictions. If you can provide me with a sample config.toml file that frees the network restrictions, I would appreciate it.
With the values:
[sandbox_workspace_write]
network_access = true
in my config.toml, network access is still restricted. Nothing seems to clear it unless the sandbox mode is "danger-full-access".
Same issue here on osx. Trying to setup an automation to connect to a db. Works in the terminal but fails to connect in codex app.
With the latest build I was able to change the sandbox settings to workspace write and check the "allow network access". After restarting codex my automations can access the network!
<img width="1759" height="630" alt="Image" src="https://github.com/user-attachments/assets/a3cbc08d-bf67-47f1-b545-480a6ab39e3f" />
This feature request hasn't received enough upvotes, so I'm closing it.