Codex Desktop Full access enabled, but new chats still launch with network disabled

Well honestly this sounds more like a state propagation/persistence bug than user misconfiguration.

The interesting part is that:

• global config shows network_access = true

• but newly created threads still persist sandboxPolicy.networkAccess:false

And that makes it feel like the thread launcher is either:

• reading from a stale permission snapshot

• caching old sandbox metadata

• or using a separate state source entirely from ~/.codex/config.toml.

So the partial allowlisted network behavior probably explains the confusing diagnostics too, some commands bypassing the broader sandbox restriction makes it look “partially enabled” even though the effective sandbox policy is still false​

Wouldn’t surprise me if thread creation is persisting an older default policy somewhere internally instead of honoring the current desktop config.