[Windows][Daybreak] Side chat can no longer use Daybreak after Daybreak became a toggle

What version of the Codex App are you using (From “About Codex” dialog)?

Powered by Codex & OWL
Version 26.911.61220
Release date: 2026-09-17

What subscription do you have?

ChatGPT Pro with Daybreak access

What platform is your computer?

Windows x64

What issue are you seeing?

After Daybreak changed from a separately selectable model to a toggle on top of GPT-5.6 Sol, side chats appear to have lost Daybreak support.

Before this change, I could select the Daybreak model directly and use it in a side chat. In the current build, Daybreak is enabled through the new toggle in the main thread, but side chat does not expose or inherit that toggle, so the side chat runs without Daybreak.

This looks like a regression introduced by the model-to-toggle migration rather than an account eligibility issue: Daybreak works in the normal/main thread on the same account.

What steps can reproduce the bug?

1. Use an account with Daybreak access.
2. Open Codex App 26.911.61220.
3. Start or open a normal thread using GPT-5.6 Sol.
4. Enable the Daybreak toggle.
5. Open a side chat from that thread.
6. Observe that there is no way to enable Daybreak for the side chat, and the parent thread's Daybreak setting is not inherited.

What is the expected behavior?

Side chat should support Daybreak when the account has access, either by:

• inheriting the parent thread's Daybreak state, or
• exposing the Daybreak toggle in the side chat itself.

The model-to-toggle migration should not remove functionality that was available when Daybreak was directly selectable as a model.

Additional information

The main thread can use the new Daybreak toggle normally. The problem appears specific to side chats / ephemeral side threads.

I searched existing open issues for Daybreak + side chat / ephemeral-thread combinations and did not find one describing this specific regression.

Reproduce the regression in Codex App 26.911.61220 on Windows x64 using an account with Daybreak access, following the six listed steps. Start by tracing how the main thread's Daybreak toggle is handled when opening a side chat or ephemeral side thread. Done means the side chat either inherits the parent Daybreak state or exposes its own toggle.