Codex alpha adds provider controls and API key Daybreak support
A new Codex alpha adds custom provider settings and API key Daybreak controls. Model and server access requirements still apply.

OpenAI published Codex 0.162.0 alpha 9 on October 3 at 01.24 UTC. The developer preview remains a prerelease, and its release page supplies only a version label. The implementation commits provide the detail behind two changes worth examining.
API key accounts reach the Daybreak controls
The Daybreak interface change lets accounts using an OpenAI API key reach the terminal client’s Daybreak controls and policy notices when support is enabled. The code keeps a crucial boundary intact. The model catalog and connected server still determine access to the program. Seeing the control does not establish that an account has permission to use a particular cyber model.
The change applies consistent eligibility checks when a turn starts, continues or retries. For API key accounts, the client sends the selected program when Daybreak is on and leaves that selection out when it is off. The commit includes request lifecycle and command tests.
Provider controls for search and context
A separate provider configuration change adds optional settings for custom providers compatible with the Responses API. Setting external_web_access to false keeps hosted web search from using the live web. That setting has a specific scope. It is not a firewall for every tool or network request.
The remote_compaction setting accepts v2 to send context compaction requests through the Responses endpoint, or unsupported to use local compaction. Leaving either capability unspecified preserves existing provider defaults. Model and turn settings may impose further restrictions.
The added tests check default preservation and a custom provider request using cached search with V2 compaction.
Check the behavior before changing a workflow
For a team evaluating the preview, the useful question is whether its own account and provider behave as expected. A controlled trial should check access with Daybreak both on and off, then inspect search and compaction requests against the provider’s documented support. Keep that trial separate from work whose interruption would have a material cost.
ByteForward inspected the implementation and test code for this report. We have not run the alpha binary or independently verified live account access. Added tests show what the project intends to check, but they do not establish compatibility with every hosted endpoint.
This follows our coverage of the stable Codex CLI 0.160.0 update, which addressed reconnect recovery, model catalogs and optional review features. The new provider and Daybreak controls belong to the alpha preview discussed here. Teams should record the exact build used when comparing results.
Original AI generated conceptual illustration of configurable access and provider controls



