Add Atlas Cloud LLM provider - #114
Open
binyangzhu000-sudo wants to merge 3 commits into
Open
Conversation
Resolve the conflict in server/tests/llmProviders.test.js by keeping both sets of assertions: main's new deepseek-v4-flash checks and this branch's Atlas Cloud checks live in the same test, so neither side is dropped. The provider registration, capability entry, shared provider id and RAG embedding exclusion merged without conflict; verified that atlascloud is still present and correctly placed in each of them.
One conflict in server/tests/llmProviders.test.js, where this branch's Atlas Cloud provider assertions and an upstream test were added at the same point. Both kept. Signed-off-by: binyangzhu000-sudo <binyangzhu000@gmail.com>
Author
|
已同步 |
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.
Summary
https://api.atlascloud.ai/v1andqwen/qwen3.5-flash, withdeepseek-ai/deepseek-v4-proin the fallback model listATLASCLOUD_API_KEYplusATLAS_CLOUD_API_KEYaliases for API key, base URL, and model env fallbackTests
corepack pnpm install --frozen-lockfile --ignore-scriptscorepack pnpm --filter @ai-novel/server prisma:generatecorepack pnpm --filter @ai-novel/shared buildcorepack pnpm --filter @ai-novel/server buildnode --test server/tests/llmProviders.test.jscorepack pnpm --filter @ai-novel/server lintcorepack pnpm --filter @ai-novel/client typecheckgit diff --checkgit diff --cached --checkNote: the focused Node test logs the existing local SQLite
APIKeytable-missing message while exercising the no-database fallback path, but all assertions pass. Atlas Cloud live model catalog was checked and contains bothqwen/qwen3.5-flashanddeepseek-ai/deepseek-v4-pro.