language_models: Support fast mode on ChatGPT subscription provider#57436
Merged
Conversation
Maps the existing `Speed::Fast` plumbing onto OpenAI's `service_tier: "priority". Relevant docs [here](https://platform.openai.com/docs/api-reference/chat/create#chat-create-service_tier). Like for the existing Anthropic fast mode we have a `Model::supports_priority` method for the variants on openai.com/api-priority-processing. Pro, nano, and legacy gpt-4 are excluded; Custom defaults to false. This is gated to staff only for now, until we have the mechanism to require confirmation before you enable fast mode.
b45d134 to
e61ee34
Compare
bennetbo
approved these changes
May 27, 2026
Member
|
We should probably add release notes, but looks good! |
Contributor
Author
|
Ah good catch! Fixing that. |
Contributor
|
TomPlanche
pushed a commit
to TomPlanche/zed
that referenced
this pull request
Jun 2, 2026
…ed-industries#57436) Same mechanism as for BYOK: `service_tier == priority`. Most of the work is already done. When validating this in manual testing, I noticed we get back `service_tier == auto` in the response, unlike in the regular OpenAI API scenario with BYOK, but apparently [it doesn't mean priority tier wasn't applied](openai/codex#14204 (comment)). It's not a hard confirmation, but the model does seem to respond faster when I toggle fast mode on. Release Notes: - Added Fast Mode (priority service tier) support to OpenAI models used through the ChatGPT subscription provider.
This was referenced Jun 3, 2026
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
3 participants
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.
Same mechanism as for BYOK:
service_tier == priority. Most of the work is already done. When validating this in manual testing, I noticed we get backservice_tier == autoin the response, unlike in the regular OpenAI API scenario with BYOK, but apparently it doesn't mean priority tier wasn't applied. It's not a hard confirmation, but the model does seem to respond faster when I toggle fast mode on.Release Notes: