feat(codex): choose a cyber access program for Daybreak-eligible models#27006

Continued in #27928 with the rebased commits and the before/after evidence requested below. GitHub rejected reopening this PR after the branch rebase.

Problem

OpenAI's Daybreak programme only applies to a Codex app-server turn when that turn's turn/start carries cyberAccessProgram. The daybreak setting in config.toml and saved thread preferences do not reach app-server turns (OpenAI guide). T3 never sent the field, so a user with Daybreak access cannot use it from T3. The turn/start encode schema in effect-codex-app-server also dropped the field, because Codex marks it experimental and leaves it out of the stable JSON schema the generator reads.

Change

• CodexProvider.ts: models whose model/list entry lists a programme other than standard in availableAccessPrograms.cyber get a "Cyber Access" select. Its options are "Automatic" (the default) plus the programmes Codex lists. Other models are unchanged.

• CodexAdapterV2.ts: buildCodexTurnStartParams sends the chosen programme on every turn. "Automatic" omits the field, so Codex keeps its current behaviour.

• client.ts and the adapter's turn/start schema: add cyberAccessProgram with Schema.fieldsAssign, as T3 already does for collaborationMode and additionalContext. Without this, the client strips the field before it reaches Codex. No generated code changes.

• CodexProvider.ts: a bare custom Codex model borrows the first built-in model's options, but not Cyber Access, because Daybreak eligibility is per model.

• docs/user/providers-codex.md: a short "Use Daybreak" section.

delegate_task checks options against the model's option list, so agents can set the option with no further change.

Scope and approval

Proposed in https://github.com/pingdotgg/t3code/discussions/26995.

This is a configuration option for a capability Codex already has. The app server accepts cyberAccessProgram, the Codex CLI exposes the same setting as /daybreak, and T3 already decodes availableAccessPrograms from model/list. The option controls only that one turn parameter, and it appears only on models where Codex offers a Daybreak programme.

Verification

Focused tests:

• CodexProvider.test.ts: there is no select for a standard-only model, and the expected options appear for ["standard", "daybreakBlue"].
• CodexProvider.test.ts: a custom model that borrows a Daybreak-eligible model's options gets reasoning but not Cyber Access. It fails without the fix.
• CodexAdapterV2.test.ts: the field is omitted when nothing or "Automatic" is chosen, and set for standard and daybreakBlue.
• CodexAdapterV2.test.ts replay test: cyberAccessProgram: "daybreakBlue" reaches the outbound turn/start frame. With the client.ts change reverted, this test fails because the client strips the field.

Rebased onto main at d92c437baa19; current head is e960980a5f6c. git range-diff confirms both original commits are unchanged by the rebase, with authorship preserved. vp run check:changed passed: format, lint, both knip checks, GraphQL generation, typecheck (4 packages), and 5 test files (137 tests).

Browser verification on the rebased branch: GPT-6-Luna offers Automatic, Standard, and Daybreak Blue; selecting Daybreak Blue survives a reload. GPT-6.1-Sol keeps its existing options without Cyber Access. Captures compare current main and the rebased branch using the same isolated environment and 1280 × 800 viewport.

Original implementation verification (not repeated during this rebase): live checks against Codex 0.164.0 with a ChatGPT account approved for Daybreak Blue:

• model/list returned ["standard", "daybreakBlue"] for gpt-6-sol, gpt-6-luna and the gpt-5.6 models, ["daybreakBlue"] for gpt-daybreak-blue-latest, and ["standard"] for gpt-6.1-sol, gpt-6.1-terra and gpt-6-astra.
• A turn on gpt-6-sol with cyberAccessProgram: "daybreakBlue" completed normally.
• The same turn on gpt-6.1-sol failed with 403 Daybreak isn't available for this model, so the backend reads the field. This is why the select only appears where Codex lists a Daybreak programme.

Not checked:

• Codex returns no field that confirms which programme a turn used.
• Codex-native subagents: updateSubagentSelection rebuilds only reasoningEffort and serviceTier, so a native subagent spawned mid-turn does not inherit the choice. I left that out of this PR to keep it to one problem.

Before / after UI evidence

Matching captures from the same isolated development environment at 1280 × 800. Before: main at d92c437baa19. After: rebased PR at e960980a5f6c.

Eligible model: GPT-6-Luna

Before: the model options have reasoning, service tier, and permissions, with no Cyber Access choice.

After: Cyber Access offers Automatic, Standard, and Daybreak Blue. Daybreak Blue is selected and survives a page reload.

Unsupported model: GPT-6.1-Sol

Before: the model options show reasoning, service tier, and permissions.

After: the same controls remain, with no Cyber Access choice.

Original implementation by Martin Meredith, assisted by Claude Opus 5.5 in Claude Code. Rebased and verified with gpt-6.1-sol in the Codex harness through T3 Code.

🤖 Generated with Claude Code