Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Revert #19053: Fast service tier should not be the default [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19230•Fetched 2026-04-24 05:58:19
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
1
Author
nwparkernwparker
Participants
etraut-openaietraut-openainwparkernwparker
Timeline (top)
labeled ×4unlabeled ×2closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Problem

#19053 makes Codex's Fast service tier the default for eligible ChatGPT plans (enterprise and business-like) when no explicit service_tier is set. Users who want standard routing have to either set service_tier explicitly or persist a new [notice].fast_default_opt_out = true marker.

This inverts the prior contract: service_tier used to flow directly from config.service_tier — what the user configured was what got sent. After #19053, core silently resolves an unset config to Fast based on plan eligibility.

Why this should be reverted

  • Opt-out instead of opt-in for a routing/cost-relevant behavior. Fast tier has different performance, availability, and (for some callers) billing characteristics. Changing routing based on plan detection, without the user asking for it, is the kind of implicit behavior change that should at minimum be opt-in.
  • New persisted config surface ([notice].fast_default_opt_out) exists only to undo the new default. That's a strong signal the default itself is wrong — if users need a durable marker to say "no, really, use standard," the managed default is fighting them.
  • service_tier: null now means "explicit standard" rather than "unset." This overloads the absence of a value with intent, which is hard to reason about and breaks the natural reading of the config.
  • TUI/status surfaces now diverge between config.service_tier (what's configured) and the "effective" service tier (what core resolved). Two sources of truth for the same concept is a maintenance hazard.

Proposed fix

Revert #19053. If Fast-by-default for enterprise plans is still desired, reintroduce it as an opt-in — e.g., a [notice].fast_default_opt_in flag, a first-run prompt, or a plan-scoped config default that's visible in config.service_tier rather than resolved behind it.

A clean revert is already prepared on a fork: https://github.com/nwparker/codex/tree/revert-19053-fast-default-enterprise

Happy to open a PR if a maintainer wants to move forward.

Made with Orca 🐋

extent analysis

TL;DR

Revert the changes introduced in #19053 to restore the original behavior where service_tier flows directly from config.service_tier, and consider reintroducing Fast-by-default for enterprise plans as an opt-in feature.

Guidance

  • Review the proposed fix and the prepared revert on the fork (https://github.com/nwparker/codex/tree/revert-19053-fast-default-enterprise) to understand the changes needed to restore the original behavior.
  • Consider the implications of introducing Fast-by-default for enterprise plans as an opt-in feature, such as adding a [notice].fast_default_opt_in flag or a plan-scoped config default.
  • Evaluate the potential impact on users who have already been affected by the changes introduced in #19053 and plan for a smooth transition.
  • Test the reverted changes to ensure that the service_tier configuration behaves as expected and that the effective service tier matches the configured value.

Example

No code snippet is provided as the issue does not contain specific code examples, but the proposed fix involves reverting the changes introduced in #19053 and potentially introducing a new opt-in flag or config default.

Notes

The proposed fix assumes that the changes introduced in #19053 are the primary cause of the issue, and reverting them will restore the desired behavior. However, additional testing and verification may be necessary to ensure that the fix does not introduce new issues.

Recommendation

Apply the proposed revert and consider introducing Fast-by-default for enterprise plans as an opt-in feature, as this approach prioritizes user control and transparency over implicit behavior changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#generation error#database connection#vector store#embedding generation#cache error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Revert #19053: Fast service tier should not be the default [1 comments, 2 participants]