Evidence record / codex

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

2026-10-24-codex-stable-updater-requests-now-require-successfully-loaded-network-policy

Stable updater requests now require successfully loaded network policy. The updater client factory now propagates configuration failure and activates the embedded network policy, replacing the older fallback to a default HTTP client. The tag includes tests for configuration failure and denied destinations. The standalone MCP path also acquired network-policy enforcement, first contained in 0.163.0. This does not turn the updater into part of the invoking CLI process: saved network settings govern it, and CLI -c overrides do not reach it.

Channel: tagged-release. Half: defect. Date: 2026-10-15.

Operator consequence: The profile’s wait for a stable tag is settled. Restricted fleets can test 0.164.0 with invalid configuration and blocked destinations before reconsidering automatic updates. Continue recording CLI and running-daemon versions separately. The human task moves from waiting for a release to verifying the fleet’s actual saved policy; no network or updater probe was run here.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-codex-stable-updater-requests-now-require-successfully-loaded-network-policy

Profile citations

  • Codex / claim / stable-updater-network-policy
  • Codex / posture / governance

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact