Skip to main content
Reasoning controls are model and protocol capabilities, not one universal provider option. Polyglot represents caller intent with ReasoningSelection and translates it only at the provider request-body boundary.

Named Effort

The portable effort vocabulary is minimal, low, medium, high, xhigh, and max. This vocabulary is a superset, not a promise that every model accepts every value. Polyglot checks the selected model’s curated capability profile and rejects unsupported or lossy mappings before sending the request.

Other Selection Kinds

Providers expose several distinct reasoning controls, so the unified type is a tagged selection rather than a nullable effort string:
providerDefault() is non-invasive: Polyglot emits no reasoning field, so existing raw options and provider defaults remain unchanged. An explicit typed selection conflicts with raw keys such as reasoning_effort, reasoning, or thinking; remove the raw key before using withReasoning().

Curated Capability Matrix

Capabilities are resolved for the model and protocol together. Unknown model IDs fail closed for explicit reasoning selections; Polyglot does not infer support from a provider name or a model-name substring. DeepSeek documents medium and xhigh as aliases that behave like high. Polyglot records those as lossy mappings and does not accept them by default; callers can select high explicitly and retain truthful effective intent.

Capability Inspection

Driver capabilities expose a structured reasoning() value. It reports whether the profile is known, accepted selection kinds, effort mappings, budget bounds, provider-default behavior, and visibility of reasoning content or token counts. The legacy supportsReasoningEffort() accessor remains as a derived compatibility projection.