[Docs] Explain model reasoning effort defaults - #45
Draft
zoomote[bot] wants to merge 1 commit into
Draft
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
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.
What changed
The Settings Management guide now explains how Zoo Code chooses model reasoning effort when no user value is saved, how models without an off mode fall back to a supported effort, how explicit
Nonebehaves, and what happens when users switch models.Why this change was made
This documents the corrected behavior delivered for Zoo-Code issue #1348, so users can distinguish model defaults from an explicit decision to disable reasoning.
Impact
Users can now understand why a reasoning effort is selected automatically and how to keep optional reasoning disabled when that is their intended setting.
Related PRs
Screenshots