Repository navigation
Add Atlas Cloud AI provider - #16
binyangzhu000-sudo wants to merge 4 commits into
Conversation
One conflict, in the provider picker in utils/credential-manager.js: upstream refreshed the labels for every entry (GPT-5.6, Gemini 3.7, OpenRouter 400+, Kimi K3) while this branch had inserted an Atlas Cloud row among the older labels. Took upstream's list verbatim and re-inserted only the Atlas row, in its original position after OpenRouter. Signed-off-by: binyangzhu000-sudo <binyangzhu000@gmail.com>
|
Synced with Took your list verbatim — so the updated model names are preserved — and re-inserted only the Atlas row in its original position after OpenRouter. Picking the wrong side here would have silently reverted your label updates. Also confirmed all four Atlas touchpoints survived the merge ( Diff against current Disclosure: I work at Atlas Cloud. |
Resolve the credential-manager conflict: keep upstream's refreshed provider labels and the new DeepSeek/MiniMax entries, and keep the Atlas Cloud entry in the missing-provider message and the setup picker. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
|
Synced with Verified locally: |
|
Updated the branch with current |
Summary
ATLASCLOUD_API_KEYin example config and cover Atlas Cloud credential validation in testsValidation
npm install --ignore-scripts --package-lock=false --no-audit --no-fund(temporary local install without changing lockfile)npm rebuild sqlite3npm test(16 passed)npm run lint(passes with existing warnings)node --check walkthrough.js utils/credential-manager.js utils/ai-text-service.js test.jsgit diff --check/v1/modelscheck returned 118 models and confirmedqwen/qwen3.5-flashanddeepseek-ai/deepseek-v4-proNo root README changes.