feat: add Atlas Cloud as LLM backend for agentic game coding#43
Open
lucaszhu-hue wants to merge 2 commits into
Open
feat: add Atlas Cloud as LLM backend for agentic game coding#43lucaszhu-hue wants to merge 2 commits into
lucaszhu-hue wants to merge 2 commits into
Conversation
OpenGame already supports any OpenAI-shaped endpoint via the existing `openai-compat` provider and the agent runtime's OPENAI_BASE_URL flow. Atlas Cloud speaks that same shape at https://api.atlascloud.ai/v1, so it plugs in as a single backend for the reasoning / GDD / classifier loop, ABC-notation audio, and OpenAI-shaped image routes — no code changes needed. This is a docs + config-only change: - README: top-of-file Atlas Cloud block (logo, blurb, collapsible official model list) plus openai-compat examples in the Authentication / provider sections. - docs/users/configuration/api-keys.md: list Atlas Cloud in the provider family table and add a dedicated single-backend example. - .env.example: commented Atlas Cloud snippets for the main agent LLM and the reasoning modality. - docs/atlas-cloud-logo.png: logo asset. No defaults are changed and no credentials are added. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- default LLM model -> deepseek-ai/deepseek-v4-pro (reasoning, max_tokens>=512) across README auth example, .env.example, and api-keys.md examples - README LLM list expanded to the full official 59-model catalog - drop GET /v1/models as a model source; point to the model list page Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
OpenGame already speaks the OpenAI REST shape in two places: the agent runtime (
OPENAI_API_KEY/OPENAI_BASE_URL/OPENAI_MODEL) and theopenai-compatprovider used by thereasoning,image, andaudiomodalities. Atlas Cloud is an OpenAI-compatible inference aggregator athttps://api.atlascloud.ai/v1that fronts 300+ models (Claude, GPT, Qwen-Coder, DeepSeek, GLM, Kimi, ...), so it drops in as a single backend without any code changes.This PR is docs + config only — no defaults are changed, no runtime behavior is altered, and no credentials are added.
Changes
openai-compatusage examples in the existing Authentication and provider-config sections.reasoningmodality.Why this PR
It gives OpenGame users a one-key path to many code/reasoning and image models behind a single OpenAI-compatible endpoint, which fits the agent loop, the GDD/classifier reasoning step, and the ABC-notation audio model. Because it reuses the existing
openai-compatplumbing, there is nothing new to maintain.Validation
POST https://api.atlascloud.ai/v1/chat/completionswithdeepseek-ai/DeepSeek-V3-0324returns a normal chat completion.packages/core/src/services/providerConfig.tsthatopenai-compatonly needs*_BASE_URL+*_MODEL(trailing slashes are trimmed), which matches the documentedhttps://api.atlascloud.ai/v1usage.Links
I'm happy to open a tracking issue first or adjust the logo size / placement to match your README conventions if you'd prefer.