Add reasoning_effort to openai compatible provider for grok-mini

[amittell]

Context

Allows the use of grok3-mini-high-beta and grok3-mini-high-fast-beta using OpenAI compatible provider.

https://www.reddit.com/r/Bard/comments/1jw8lap/grok_3_mini_beta_overtakes_25_pro_in_livebench/

Implementation

Add support for reasoning_effort parameter for grok3-mini models.

Screenshots

before	after

|

How to Test

Set up Grok in the Open AI Compatible provider, choose grok3-mini-beta or grok3-mini-fast-beta. Choose the reason_effort level from the dropdown (default = low).

---

Important

Add reasoning_effort support for Grok 3 Mini models in OpenAI compatible provider with UI and tests.

• Behavior:
  • Adds reasoning_effort parameter support for Grok 3 Mini models in OpenAiHandler in openai.ts.
  • Updates ExtensionMessage and WebviewMessage to include reasoningEffort and grokReasoningEffort.
  • Introduces GrokReasoningSettings component in ApiOptions.tsx for UI selection of reasoning effort.
• Tests:
  • Adds tests in openai.test.ts to verify reasoning_effort parameter inclusion and processing of reasoning_content.
• UI:
  • Displays GrokReasoningSettings in ApiOptions.tsx when Grok 3 Mini models are selected.

^{This description was created by for fdc8085. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: fdc8085

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

The label and option texts in GrokReasoningSettings are hard-coded. For consistency with our internationalization standards, consider wrapping these strings with the translation function (e.g. use t('...')).

[cte]

Thanks for this! I actually started working on a version of this that will also work with OpenRouter: #2483

Closing in favor of that PR (which I hope to get out tomorrow).