chore: add warning for providers that do not support new reasoning parameter#13649
Merged
felixarntz merged 4 commits intomainfrom Mar 20, 2026
Merged
chore: add warning for providers that do not support new reasoning parameter#13649felixarntz merged 4 commits intomainfrom
felixarntz merged 4 commits intomainfrom
Conversation
This was referenced Mar 19, 2026
lgrammel
approved these changes
Mar 20, 2026
felixarntz
added a commit
that referenced
this pull request
Mar 20, 2026
#13648) ## Background The new top-level `reasoning` parameter was added to the AI SDK spec and core in #13553. Providers need to be migrated to translate this parameter into their native reasoning/thinking configuration. ## Summary Migrates 7 providers to support the new top-level `reasoning` parameter: - **deepseek**: Maps `reasoning` to existing thinking support (already had infrastructure, just needed wiring) - **groq**: Maps `reasoning` to `reasoning_effort` in provider options - **xai**: Maps `reasoning` to `reasoning_effort` for both chat and responses models - **openai-compatible**: Maps `reasoning` to `reasoning_effort` in provider options - **open-responses**: Maps `reasoning` to `reasoning.effort` in the responses format - **alibaba**: Maps `reasoning` to `enable_thinking` + `thinking_budget` via token budget calculation - **cohere**: Maps `reasoning` to `thinking.type` + `thinking.token_budget` via token budget calculation - **fireworks**: Uses **openai-compatible** Together with #13649, this completes the work on #12516. ## Manual Verification Relevant examples were updated or added, then run for verification. ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review) ## Future Work N/A ## Related Issues See #12516.
Contributor
|
🚀 Published in:
|
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
2 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.
Background
A new top-level
reasoningparameter was added to the AI SDK spec in #13553 and is supported ingenerateText/streamText. Providers that don't natively support reasoning configuration need to emit an unsupported warning when a custom reasoning value is passed, rather than silently ignoring it.Summary
perplexity,mistral, andprodiaproviders whenisCustomReasoning(reasoning)returnstruearchitecture/provider-abstraction.mdexplaining how providers should handle thereasoningparameter (effort mapping, budget mapping, or unsupported warning).Together with #13648, this completes the work on #12516.
Manual Verification
N/A
Checklist
pnpm changesetin the project root)Future Work
N/A
Related Issues
See #12516.