docs: correct GPT-5 token limit scope to GitHub Models only#55
Open
detail-app[bot] wants to merge 1 commit into
Open
Conversation
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
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.
Updated documentation and comments to reflect that the 7K token input
cap applies only to GPT-5 served via GitHub Models, not the entire
GPT-5 family. GPT-5 models served via OpenAI direct or the LLM gateway
use the 100K default token budget.
Without this correction, a developer might incorrectly assume all GPT-5
models have an 8K input limit and over-truncate prompts for models that
support far larger contexts.
Introduced by commit ce24b66 (@WilliamAGH, #52)
Doc Drift PRs can be configured here.