Description
So far, we're handling all reasoning / thinking configuration via providerOptions. While this has historically made sense, over time many providers have adopted this, often in somewhat similar ways. We should consider making it part of the top-level spec.
Questions to discuss and answer:
- Which naming convention do we align with for our abstraction? "reasoning" or "thinking"?
- Which config parameters do we allow controlling, and how?
- How do we map our abstraction config to the individual provider requirements around this?
A good starting point is to review providers with support on how they handle these aspects. From there, we can converge towards a reasonable abstraction.
AI SDK Version
No response
Code of Conduct
Description
So far, we're handling all reasoning / thinking configuration via
providerOptions. While this has historically made sense, over time many providers have adopted this, often in somewhat similar ways. We should consider making it part of the top-level spec.Questions to discuss and answer:
A good starting point is to review providers with support on how they handle these aspects. From there, we can converge towards a reasonable abstraction.
AI SDK Version
No response
Code of Conduct