Skip to content

feat: add Atlas Cloud provider preset - #925

Open
binyangzhu000-sudo wants to merge 5 commits into
TraderAlice:devfrom
binyangzhu000-sudo:codex/atlas-cloud-provider
Open

binyangzhu000-sudo wants to merge 5 commits into
TraderAlice:devfrom
binyangzhu000-sudo:codex/atlas-cloud-provider

Conversation

@binyangzhu000-sudo

Copy link
Copy Markdown

Summary

  • add Atlas Cloud to the built-in AI provider preset catalog
  • configure its OpenAI-compatible Chat Completions endpoint and default model
  • register the routed model semantics and keep credential injection defaults aligned

Verification

  • pnpm exec vitest run src/ai-providers/preset-catalog.spec.ts src/ai-providers/model-semantics.spec.ts src/workspaces/cli/shim.spec.ts services/uta/src/domain/trading/brokers/presets.spec.ts (80 passed)
  • pnpm exec tsc --noEmit
  • full pnpm test: 3828 passed, 9 skipped; two unrelated tests timed out under the full parallel run and passed when rerun in the focused set; the catalog-contract failure found by the full run was fixed before the focused rerun
  • parsed the preset and used its endpoint/model with the OpenAI client against the live Atlas Cloud API (123 models; default model present; chat completed)
  • git diff --check

Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
@vercel

vercel Bot commented Jul 31, 2026

Copy link
Copy Markdown

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

A member of the Team first needs to authorize it.

@RainMona

Copy link
Copy Markdown
Contributor

云端代理审阅(以 upstream dev @ 47e8651b 为准)

结论

仍可行动、值得接,但需重基 + CI 绿。

现状

  • presetProviders 仍无 Atlas Cloud;产品需求仍成立。
  • 与 dev 有冲突(含 PLANS.md);需 rebase 到当前 dev。
  • Checks:Vercel 授权噪声;项目 CI 未见到结果。

建议

  1. Rebase 到 dev,解冲 PLANS.md(不要带无关的计划行)。
  2. 确认仅触及 preset / 文档,不扩大到认证核心逻辑。
  3. 项目 CI 绿后再合入。

binyangzhu000-sudo and others added 2 commits August 17, 2026 13:36
All three conflicts were the same both-sides-added-a-preset shape: upstream
added an openrouter entry in the exact rows this branch adds atlas-cloud, in
DEFAULT_MODEL_BY_PRESET and in the two matching spec expectations. Both
entries are kept everywhere, openrouter first in upstream's position.

Checked the auto-merged side too: the atlas-cloud entry in model-semantics.ts
survived the merge intact.

vitest src/ai-providers -> 42 passed; tsc --noEmit clean.
@binyangzhu000-sudo

Copy link
Copy Markdown
Author

Synced with master (1305 commits). All three conflicts were the same shape — upstream added an openrouter preset in the exact rows this branch adds atlas-cloud:

  • preset-catalog.ts → DEFAULT_MODEL_BY_PRESET
  • preset-catalog.spec.ts → the two matching expectation objects

Both entries are kept everywhere, openrouter first in upstream's position.

I also checked the auto-merged side rather than assuming a clean merge is a correct one: the atlas-cloud entry in model-semantics.ts came through intact.

Verification on the merged branch:

  • vitest run src/ai-providers → 42 passed (3 files)
  • tsc --noEmit → clean

No conflicts remain.

This PR targets dev, but the previous sync on this branch merged
upstream/master instead. That pulled master's 65 release commits in and
put a version bump and a CI workflow edit into the diff, none of which
belong to an Atlas Cloud preset. Merging dev this time absorbs all of it:
the only conflicts were the two package.json versions, both resolved to
dev's 0.93.1-beta, and the diff against dev is now the three
src/ai-providers files this PR is actually about.

Verified: vitest run — 800 files, 7039 passed, 4 skipped, zero failures;
tsc --noEmit — zero errors.
@binyangzhu000-sudo

Copy link
Copy Markdown
Author

Synced with dev — and corrected a mistake in the previous sync on this branch.

This PR targets dev, but the earlier sync merged upstream/master instead. That pulled master's
65 release commits in and put a version bump (0.93.0) and a CI workflow edit into the diff, none of
which belong to an Atlas Cloud preset. Merging dev this time absorbs all of it: the only conflicts
were the two package.json versions, both resolved to dev's 0.93.1-beta, and the diff against
dev is now exactly the three src/ai-providers/ files this PR is about — 64 insertions, down from
6 files / 67.

The preset itself is unchanged. I checked its shape against the other third-party presets in
preset-catalog.ts and it carries the same fields (zodSchema, regions, models, setup,
writeOnlyFields) with no hardcoded pricing or other data that would go stale.

Verified:

  • vitest run — 800 files, 7039 passed, 4 skipped, zero failures
  • tsc --noEmit — zero errors

Resolve the package.json / packages/cli/package.json version conflicts
in favour of dev. The diff against dev remains the three
src/ai-providers files for the Atlas Cloud preset.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Signed-off-by: binyangzhu000-sudo <224954946+binyangzhu000-sudo@users.noreply.github.com>
@binyangzhu000-sudo

Copy link
Copy Markdown
Author

Thanks for the review. Re-synced with the current dev (5da8dfc).

  1. Rebase / conflicts: ✅ Merged dev into the branch. The only conflicts were the version fields in package.json and packages/cli/package.json; both resolved to dev's values. PLANS.md no longer conflicts.
  2. Scope: ✅ The diff against dev is exactly three files under src/ai-providers/ (64 insertions): the atlas-cloud preset, its model semantics, and the catalog spec. No auth or trading code is touched.
  3. CI: the only check shown on the PR is the Vercel authorization notice (needs a team member to authorize; unrelated to the code). I could not see the project's own CI results, so I ran the checks locally on the merged tree.

Verified locally: tsc --noEmit is clean; vitest run src/ai-providers src/workspaces/cli/shim.spec.ts services/uta/.../presets.spec.ts gives 7 files, 118 tests passed. A live call using the preset's parsed defaults (base URL + deepseek-ai/deepseek-v4-pro) against the Atlas Cloud gateway returned HTTP 200, and the model id is still listed in /v1/models.
Not run: the full pnpm test suite.

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants