RAP Sheet home
Install the bug reporting skill
Rank, 14 days: 81 on the Codex sheet
17 people reported

All time, since Sep 30, including 5 thumbs-up on GitHub.

Full access/network setting not applied

“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/themes/190/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

Fading. 1 report or thumbs-up in the last 7 days and 2 the week before, down from 8 a week at the late-October peak.

3 bugs in this theme

  1. Shell network blockedNo workaround yet7 people
  2. Network blocked despite setting onNo workaround yet6 people
  3. Full access ignored in new chatsNo workaround yet4 people

What's included

  • Shell commands fail DNS lookups or connections (WSAEACCES 10013, "Could not resolve host", "Operation not permitted") while CODEX_SANDBOX_NETWORK_DISABLED=1
  • Session reports workspace-write and restricted network although Full access is selected or network_access = true is in config.toml
  • New chats lack the Full access/permission selector while an older chat with Full access works
  • Writes outside the project (Desktop folder, ~/.codex) are denied under a managed restricted profile after selecting Full access
  • Seen on both Windows and macOS desktop, including ChatGPT Work chats and SharePoint/SSH/package downloads

Not included

  • Missing /sandbox-add-read-dir command and EPERM on user-profile folders from an MCP worker
  • Sessions failing to start with "elevated Windows sandbox requires effective :root read access"

Original reports12, newest first

  1. [Windows / ChatGPT Work] SSH and HTTPS TCP fail with WSAEACCES 10013 after enabling network access and granting Full accessOn GitHub#57671
  2. macOS: new chats have networking disabled and no permission selector while an older Full access chat worksOn GitHub#56808
  3. [Windows Desktop] Selecting "Full access" sends permission_profile: "managed" that is not defined locally, silently falling back to workspace-writeOn GitHub#56663
  4. DNS resolution failed inside error the Codex mac appOn GitHub#56383
  5. [Windows 10][Work + Codex Desktop] Networking disabled despite enabled settings; standalone CLI HTTPS succeeds (26.1016.6573.0)On GitHub#56194
  6. macOS Desktop 26.1016.51333: new Full access chat receives managed workspace-write permissionsOn GitHub#55922
  7. [Windows / ChatGPT Work] Executor runs as CodexSandboxOffline with approval_policy=never despite internet access enabled; SharePoint downloads fail with WSAEACCESOn GitHub#55828
  8. [macOS / ChatGPT Work] Terminal DNS and HTTPS fail despite network_access=true; Sites publishing blockedOn GitHub#55307
  9. Full access selected, but local Work execution remains restricted across new chats.On GitHub#54837
  10. Codex Desktop on Windows applies networkAccess=false despite network access being enabledOn GitHub#53278
Show all 12Show only the newest 10
  1. macOS Work: Full access enabled, but terminal network access remains restrictedOn GitHub#51624
  2. [macOS][26.928.21956] New Work/project chat has no Full access control and blocked shell network; existing local chat worksOn GitHub#49768

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.

Claim a tool