Reasoning effort fix#1674
Merged
Merged
Conversation
architkumar-truefoundry
approved these changes
Jul 2, 2026
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 21342ca. Configure here.
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.

Note
Low Risk
Changes are catalog/metadata only (params and removeParams); no runtime code paths. Wrong values could mislead API clients but are easy to spot in config review.
Overview
This PR corrects how
reasoning_effortis declared on provider model YAML so clients only see the knob where it applies, with per-model allowed values.Cohere adds
reasoning_efforttodefault.yaml(defaulthigh,none/high) for chat-capable configs, and strips it from embed, rerank, and transcribe models viaremoveParams.AWS Bedrock Mantle GPT-OSS chat models now expose
reasoning_effortwithlow/medium/high.Google Vertex Anthropic chat entries are split: many Opus/Fable/Sonnet variants gain explicit
reasoning_effort(defaults and tiers likexhigh/maxwhere relevant), while Haiku 4.5 and Sonnet 4.5 entries removereasoning_effortso it is not offered on those Vertex routes.Reviewed by Cursor Bugbot for commit 888a72f. Bugbot is set up for automated code reviews on this repo. Configure here.