feat(providers): add Bailian provider options - #658
Merged
Conversation
ewen-poch
marked this pull request as ready for review
August 3, 2026 06:27
Codex ReviewVerdict: mergeable No actionable findings. Summary: Static inspection found no concrete merge-blocking defect in the pull request changes. Branch and title prechecks are valid. |
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
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
Bailian's current Qwen 3.8 and related Qwen/DeepSeek catalogs were not available as official providers. The Bailian Token Plan subscription also uses separate fixed endpoints and a smaller, model-specific catalog.
Proposed change
Bailianwith China and Global DashScope regions, Anthropic Messages, OpenAI Chat Completions, and Responses support.Bailian for Planwith its Token Plan Anthropic/OpenAI endpoints, subscription key link, curated Qwen/GLM/DeepSeek catalog, and image-input capabilities. The Plan provider does not advertise Responses support.Sources: Bailian model marketplace, Bailian for Plan model documentation, and LobeHub static Bailian icon.
Scope and non-goals
This is an additive provider-registry and Settings UI change. It does not change persistence, IPC, data relationships, or endpoint-normalization architecture. The existing
OfficialModelcontract stores context-window size but not separate maximum input, output, or chain-of-thought token limits, so the Qwen 3.8 entry records its 1M context without expanding that data model.No authenticated live calls were made because validation requires user-owned Bailian keys.
Acceptance criteria and validation
npm test -- --run src/shared/provider-registry.test.ts src/renderer/src/pages/settings/ProviderForm.render.test.tsx src/renderer/src/pages/settings/provider-form-value.test.ts→ 3 files / 91 tests passed.npm run typecheck→ passed.npm run lint→ passed with 0 errors and 18 pre-existing warnings outside this diff.npm test→ 684 files / 10,069 tests passed; six unrelated load-sensitive tests failed under the full concurrent run. Re-running those six files at lower load passed all 379 tests.git diff --check origin/main...HEAD→ passed.Review focus