macOS startup panic when SystemConfiguration DNS state is unavailable

What version of Codex is running?

codex-cli 0.116.0

Which model were you using?

Default startup path; crash happens before interactive use

What platform is your computer?

macOS Darwin 25.1.0 arm64

What issue are you seeing?

codex panics on startup if macOS SystemConfiguration DNS state is unavailable.

In my case this happens when launching codex inside the Superset desktop app terminal. In that environment:

scutil --proxy
scutil --dns

returns:

<dictionary> {
}
No DNS configuration available

Then running:

codex

crashes with:

thread 'main' (...) panicked at /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/system-configuration-0.6.1/src/dynamic_store.rs:154:1:
Attempted to create a NULL object.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Steps to reproduce

1. Launch a shell in an environment where macOS SystemConfiguration DNS state is unavailable.
2. Confirm with:

scutil --dns

1. Run:

codex

Expected behavior

Codex should not panic. It should either:

• continue without the reachability/DNS watcher, or
• emit a normal error explaining that macOS networking state is unavailable.

Actual behavior

Codex aborts with a panic from the system-configuration crate.

Additional context

• codex --version works and prints codex-cli 0.116.0
• The crash happens during full startup
• The same machine/user/install works normally in Warp, where scutil --dns returns standard resolver info
• This seems related to SCDynamicStore / DynamicStore initialization returning NULL