Skip to content

Add Atlas Cloud provider preset - #660

Open
binyangzhu000-sudo wants to merge 2 commits into
op7418:mainfrom
binyangzhu000-sudo:codex/add-atlascloud-provider-preset
Open

binyangzhu000-sudo wants to merge 2 commits into
op7418:mainfrom
binyangzhu000-sudo:codex/add-atlascloud-provider-preset

Conversation

@binyangzhu000-sudo

Copy link
Copy Markdown

Summary

  • Add Atlas Cloud as a built-in OpenAI-compatible provider preset.
  • Seed the preset with https://api.atlascloud.ai/v1, API-key auth, and live-verified default models.
  • Cover exact preset matching, catalog defaults, and runtime compatibility in the provider preset tests.

Tests

  • git diff --check
  • npx tsx --test src/__tests__/unit/provider-preset.test.ts (106 passed)
  • npx tsx --test src/__tests__/unit/provider-icon-rule.test.ts (16 passed)
  • npx eslint src/lib/provider-catalog.ts src/__tests__/unit/provider-preset.test.ts (passes with one existing _role warning in provider-catalog.ts)
  • Atlas live /v1/models check returned 118 models and confirmed qwen/qwen3.5-flash plus deepseek-ai/deepseek-v4-pro

Notes

  • npm ci is currently blocked by an upstream package-lock mismatch (@electron/windows-sign, cross-dirname, fs-extra, etc. missing from lockfile). I used npm install --package-lock=false --ignore-scripts for local dependency install and did not modify the lockfile.
  • Full npm run typecheck currently fails in unrelated existing component files (src/components/ai-elements/*, DevOutputChips.tsx, UsageStatsSection.tsx), not in the changed provider catalog files.

README / marketing compliance

  • No README changes
  • No sponsor, logo, credits, or partner promotion added

@vercel

vercel Bot commented Jul 20, 2026

Copy link
Copy Markdown

@binyangzhu000-sudo is attempting to deploy a commit to the op7418's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the area:tests PR/issue 影响面: tests label Jul 20, 2026
@binyangzhu000-sudo

Copy link
Copy Markdown
Author

Thanks. I pushed follow-up commit eb9113a69eab8eb2fda168c2154937394c1b7508 resolving the current merge conflict.

What changed:

  • Merged latest main into the PR branch.
  • Resolved src/lib/provider-catalog.ts by keeping both the existing Atlas Cloud preset and the new upstream xAI preset.
  • Updated the Atlas Cloud preset test record shape to include preset_key and protocol, matching the current provider identity type.
  • Kept the net PR diff against main limited to provider-catalog.ts and provider-preset.test.ts.

Validation:

  • npm install --package-lock=false --ignore-scripts --no-audit --no-fund
  • npm rebuild better-sqlite3
  • CODEX_DISABLED=1 npx tsx --test --import ./src/__tests__/db-isolation.setup.ts src/__tests__/unit/provider-preset.test.ts — 112 tests passed
  • npx eslint src/lib/provider-catalog.ts src/__tests__/unit/provider-preset.test.ts — 0 errors, 1 existing warning in provider-catalog.ts for _role
  • git diff --check origin/main...HEAD

Notes:

  • npm ci is currently blocked locally because package.json and package-lock.json are out of sync for Electron signing dependencies after the upstream merge.
  • npm run typecheck still reports unrelated upstream UI typing errors in src/components/ai-elements/* and src/components/settings/UsageStatsSection.tsx; the Atlas Cloud test record type errors are fixed.
  • No paid Atlas live POST was run.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:tests PR/issue 影响面: tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant