Regression: Fast mode is lost for resumed existing threads after app restart, while new threads still work

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

Version 26.730.61639

What subscription do you have?

ChatGPT Pro (20× plan).

What platform is your computer?

macOS 26.6 (25G72), arm64

What issue are you seeing?

Fast mode state is lost when an existing thread/task is resumed after restarting the Codex App.

The important distinction is:

• Fast mode works in a newly created thread.
• Fast mode was enabled in an existing thread before restarting the app.
• After quitting and reopening Codex, every existing thread resumes with the Fast-mode UI shown as disabled/off.
• Creating a new thread still allows Fast mode to work, so Fast-mode eligibility itself has not disappeared.
• This reproduces across every existing task tested, not only one particular thread.
• The confirmed symptom is the UI state. It is currently unknown whether the backend request still uses the Fast service tier.

This appears to be an existing-thread resume/UI-state persistence problem rather than Fast mode being unavailable for the account.

What steps can reproduce the bug?

1. Open Codex App on macOS.
2. Open or create a thread and enable Fast mode.
3. Confirm the Fast-mode lightning/speed control is enabled.
4. Quit the Codex App normally.
5. Reopen the app.
6. Resume the same existing thread.
7. Observe that its Fast-mode indicator is disabled/off.
8. Repeat with other existing threads and observe the same disabled/off Fast-mode UI.
9. Create a new thread and observe that Fast mode is available and works there.

What is the expected behavior?

An existing thread that had Fast mode enabled should preserve and display that state after the app restarts.

At minimum, the resumed thread UI should accurately display the effective service tier instead of showing Fast mode as disabled while new threads can still use it.

Additional information

This looks like a regression or narrower remaining case of #20769, Codex App resets Speed from Fast to Standard after restart.

The report intentionally describes this as a UI-state bug because the effective backend service tier has not been independently verified.

Issue #20769 was closed as completed on June 4, 2026 after users confirmed that a then-current update preserved the setting across restarts. The behavior is now reproducible again on the much newer macOS build 26.730.61639, specifically when resuming an existing thread.

Related state/UI reports:

• #20769
• #14689

Screenshots show the resumed existing task after restart with the Fast-mode control not enabled, while Fast mode remains functional in a new task.