feat(studio): allow manual model input for custom services#301
Open
jiashuaiLu wants to merge 1 commit into
Open
feat(studio): allow manual model input for custom services#301jiashuaiLu wants to merge 1 commit into
jiashuaiLu wants to merge 1 commit into
Conversation
Add a manual Model ID input field in the custom service configuration page. This enables users to specify a model when the provider does not support the /models endpoint (e.g. JD Cloud, private deployments). Changes: - ServiceDetailPage.tsx: add manualModel state, input field, and wiring - service-detail-state.ts: propagate manualModel to probe and save APIs - server.ts: accept manualModel in /services/:service/test and pass it to probeServiceCapabilities as preferredModel Closes: inability to use custom OpenAI-compatible endpoints without /models
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
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.
Problem
Custom OpenAI-compatible endpoints (e.g. JD Cloud, private deployments) often do not expose a
/modelsendpoint. The current Studio UI only supports auto-discovered models, making it impossible to configure and use such providers.Solution
Add a Model ID (optional) input field to the custom service configuration page. When filled, the value is passed as
preferredModelto the backend probe logic, which uses it as a fallback candidate if the/modelslist is empty.Changes
manualModelstate, input field in the custom service form, and wire it to test/save handlersprobeServiceForDetailandsaveServiceConfigto accept and forwardmanualModelmanualModelin the/services/:service/testPOST body and pass it toprobeServiceCapabilities.preferredModelHow to test
kimi-k2.5)/modelsendpoint