[binyangzhu000-sudo]

Summary

Adds Atlas Cloud (OpenAI-compatible gateway, https://api.atlascloud.ai/v1) as a named provider in the provider registry, mirroring the existing Novita / SiliconFlow gateway entries. Users can configure providers.atlascloud.apiKey (or ATLASCLOUD_API_KEY), and a base URL containing atlascloud is auto-detected.

Disclosure: I work at Atlas Cloud.

Files:

• App/memmy-agent/src/providers/registry.ts: new atlascloud ProviderSpec (gateway, openai_compat, ATLASCLOUD_API_KEY, default base https://api.atlascloud.ai/v1).
• App/memmy-agent/tests/providers/atlascloud-provider.test.ts: registry/config/kwargs tests, modelled on novita-provider.test.ts.

Provider-specific decisions:

• No stripModelPrefix: Atlas model ids are namespaced (e.g. deepseek-ai/deepseek-v4-flash) and must be sent verbatim (covered by a test).
• No frontend change: the desktop logo map is keyed by model protocol, not gateway, and other gateways (Novita, SiliconFlow) have no entry there either.

Test plan

• npx vitest run tests/providers in App/memmy-agent: 48 files / 762 tests passed (includes the new test file)
• prettier --check and eslint on the touched files: clean
• Live check through the repo's own path (Config.fromObject -> makeProvider -> OpenAICompatProvider.chat) against the real gateway with deepseek-ai/deepseek-v4-flash, maxTokens: 64: HTTP 200, response parsed (the 64 tokens were consumed by reasoning, so finishReason: "length" with reasoningContent populated; 11 prompt tokens)
• GET https://api.atlascloud.ai/v1/models returned 200 with 120 models (plain fetch; the repo has no list-models code path for gateways)
• Not run: full repo test suite, root workspace build, desktop UI. tsc --noEmit reports one error that is unrelated to this change (@memmy/knowledge not built locally).

🤖 Generated with Claude Code

[Memtensor-AI]

🤖 Open Code Review

Target: PR #730
Task: b606b9b3d531997a
Base: main
Head: add-atlascloud-provider

🔍 OpenCodeReview found 1 issue(s) in this PR.

---

1. App/memmy-agent/src/providers/registry.ts (L230-L231)

Missing hyphenated alias. normalizeProviderName("atlas-cloud") / normalizeProviderName("atlasCloud") both normalize to atlas_cloud, which does not equal the keyword atlascloud, so findByName returns null for those spellings and a forced provider assignment (provider: atlas-cloud) ends up failing in matchProvider. Other multi-word brands here already carry such an alias ("hugging-face", "ant-ling", "atomic-chat"), so adding it keeps named lookup consistent.

💡 Suggested Change

Before:

    name: "atlascloud",
    keywords: ["atlascloud"],

After:

    name: "atlascloud",
    keywords: ["atlascloud", "atlas-cloud"],

Generated by cloud-assistant via Open Code Review.

[Memtensor-AI]

✅ Automated Test Results: PASSED

All tests passed (6/6 executed). common/smoke: 6/6. Duration: 2s

Branch: add-atlascloud-provider