In the Codex Desktop APP, GitHub cannot be accessed, but the terminal can.
Resolved 💬 5 comments Opened Feb 3, 2026 by cooper-lgtm Closed Feb 3, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.9.4
What subscription do you have?
plus
Which model were you using?
gpt-5.2-codex extra high
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
_No response_
What issue are you seeing?
<img width="924" height="723" alt="Image" src="https://github.com/user-attachments/assets/a203fc45-64d7-497b-b390-65504de5c036" />
What steps can reproduce the bug?
In the Codex Desktop App, let the model commit code for you, create new branches, pull branch comments, and even make gpt curl -I https://github.com not possible. I don't know if this is a codex sandbox environment or if there is any special operation
What is the expected behavior?
_No response_
Additional information
_No response_
5 Comments
Do you have any non-default config settings in your
~/.codex/config.tomlfile? For example, are you modifying the sandbox policy by definingwritable_roots?Seems that new codex vscode extension and desktop app don't recognize
sandbox_workspace_writesettings inconfig.toml.We're tracking that in #10439.
[sandbox_workspace_write]
network_access = true
My sandbox only has the default configuration, and I haven’t configured writable_roots at all. In the Codex CLI, I can successfully run curl -I https://github.com, but the same command fails in the Codex app—only the app cannot access external network resources.
After adding sandbox_permissions = "allow" under [sandbox_workspace_write], the issue was resolved. Previously, curl only worked in the Codex CLI. Now, requests are first attempted inside the sandbox; if that attempt fails, they fall back to executing outside the sandbox.