fix: map service_tier fast to priority for Codex backend#282
Open
icebear0828 wants to merge 1 commit intomasterfrom
Open
fix: map service_tier fast to priority for Codex backend#282icebear0828 wants to merge 1 commit intomasterfrom
icebear0828 wants to merge 1 commit intomasterfrom
Conversation
The Codex backend rejects `service_tier: "fast"` in the request body
("Unsupported service_tier: fast"). The Desktop app (codex-rs) maps
`Fast` to `"priority"` before sending — align proxy behavior to match.
Previously cc1b29d stripped service_tier entirely as a workaround,
making -fast/-flex suffixes non-functional. Now the field is preserved
in both HTTP and WebSocket paths with the correct mapping.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
-fast/-flexsuffixes were completely non-functional since cc1b29d strippedservice_tierfrom both HTTP body and WS request as a workaround for backend rejecting"fast""priority"not"fast"— confirmed by reading codex-rs source (client.rs:739-741:ServiceTier::Fast => "priority")fast → "priority"and preserve the field in the request body, matching Desktop behaviorTest plan
gpt-5.4-fastreturns 200 (previously would have returned "Unsupported service_tier: fast" without the cc1b29d strip)