docs: fix per-model Shift+Tab thinking-level cycle description#3111
Open
aheritier wants to merge 2 commits into
Open
docs: fix per-model Shift+Tab thinking-level cycle description#3111aheritier wants to merge 2 commits into
aheritier wants to merge 2 commits into
Conversation
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
This documentation fix correctly changes the cycling description from "provider-specific" to "model-specific". Two inconsistencies were found in the updated examples on line 335.
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.
Documentation changes
Updates `docs/guides/thinking/index.md` to fix the description of how the TUI's Shift+Tab thinking-level cycling works after #3097 changed the behaviour from per-provider to per-model.
What was wrong
The "Changing Thinking Level at Runtime" section said:
After #3097, cycling is model-specific — each model only offers the levels its API actually accepts. The old OpenAI example implied every OpenAI reasoning model cycles through `xhigh`, but that's only true for gpt-5.2+; gpt-5, gpt-5.1, and the o-series all top out at `high`.
What was fixed
The bullet now reads:
Commits
818742d1PRs reviewed and found up to date