feat: Add reasoning and capability controls for OpenAI Compatible models #4860
Conversation
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
🦋 Changeset detectedLatest commit: 526a398 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Related to Kilo-Org#4506 and #7370 ## Summary This PR addresses the pain points around configuring reasoning and tool capabilities for custom OpenAI-compatible models (like DeepSeek R1). ## Changes - **UI**: Added checkboxes for 'Supports Reasoning', 'Supports Function Calling', and 'Supports Computer Use' to the OpenAI Compatible settings. - **UI**: Compacted the capability checkboxes into a 2-column grid layout with tooltip-only descriptions. - **Backend**: Updated OpenAiHandler to inject the 'thinking' parameter when reasoning is enabled and the model supports it. - **Backend**: Gated tool inclusion based on the 'supportsNativeTools' flag. - **i18n**: Added translation strings for the new settings. ## Findings The backend logic in base-openai-compatible-provider.ts has support for reasoning (via <think> tags) and tools, but these features were gated by flags that were unreachable from the UI for custom models.
benzntech
force-pushed
the
feat/openai-compatible-settings-improvements
branch
from
82cbecb to
8a902d2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related to #4506 and #7370
Summary
This PR addresses the pain points around configuring reasoning and tool capabilities for custom OpenAI-compatible models (like DeepSeek R1).
Findings: Existing GitHub issues (#4506, #7370) confirm that reasoning support for custom OpenAI-compatible models (like DeepSeek) has been a pain point. Code analysis revealed that the backend logic in
base-openai-compatible-provider.tshas support for reasoning (via<think>tags) and tools, but these features were gated by flags that were unreachable from the UI for custom models.Changes
OpenAiHandlerto inject thethinkingparameter when reasoning is enabled and the model supports it (supportsReasoningBinary).supportsNativeToolsflag.How to Verify
deepseek-reasoner).