Shell network blocked

“The affected newer conversation does not show that control, and its shell commands cannot resolve public hosts or send packets.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/13521/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 3 a week at the early-October peak.

Shell commands cannot reach network despite Full access or network_access config. Shell diagnostics show CODEX_SANDBOX_NETWORK_DISABLED=1 and "Could not resolve host", while the permission selector is missing in affected chats.

Is this your bug?

File my report

Where: Desktop app shell
Error text: curl: (6) Could not resolve host: api.github.com
Versions: 26.928.21956 to 26.1021.31345
Platforms: macOS
How bad: Breaks a normal workflow. Some reports say it used to work.

Part of: Full access/network setting not applied3 bugs

Network blocked despite setting on6 people
Full access ignored in new chats4 people

Not quite your bug?

Full access permissions not applied3 people

Original reports5, newest first

Oct 24, 2026macOS: new chats have networking disabled and no permission selector while an older Full access chat worksOn GitHub#56808
Oct 23, 2026DNS resolution failed inside error the Codex mac appOn GitHub#56383
Oct 19, 2026[macOS / ChatGPT Work] Terminal DNS and HTTPS fail despite network_access=true; Sites publishing blockedOn GitHub#55307
Oct 7, 2026macOS Work: Full access enabled, but terminal network access remains restrictedOn GitHub#51624
Sep 30, 2026[macOS][26.928.21956] New Work/project chat has no Full access control and blocked shell network; existing local chat worksOn GitHub#49768