API setup · Chat Completions
VS Code · Chat & Copilot + Luma Cloud
Add Luma Cloud with VS Code's Custom Endpoint model provider.
Use your Luma Cloud API key, Base URL and an available model ID with the client-specific settings below. SuperGPT desktop installation and sign-in are separate.
Before you start
- Create a Luma Cloud API key in Dashboard → API and copy a model ID from the authenticated model catalog.
- Use a VS Code version with Custom Endpoint. Organization policy may restrict bring-your-own-key models.
Set up VS Code · Chat & Copilot
- Open the native model manager
Open the Command Palette with Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux. Run Chat: Manage Language Models. This configures VS Code Chat itself; Continue, Cline, and other extensions have their own settings.
- Add Luma Cloud
Choose Add Models → Custom Endpoint and name the group Luma Cloud. Enter your API key in the prompt. Let VS Code retain the secret reference; do not paste the raw key into a project settings file.
- Configure the model
Choose Chat Completions. In the generated chatLanguageModels.json, set the model ID and full endpoint below. Retain the generated ${input:...} secret reference. Set input/output limits and tool/vision flags from the model's supported capabilities.
- Select it in chat
Save and choose the Luma Cloud model in a new chat. Agent mode requires tool calling. If the model is absent, reload VS Code and check the organization policy.
- Provider
Custom Endpoint- API type
chat-completions- Model URL
https://api.lumaos.cloud/v1/chat/completions- Model ID
MODEL_ID_FROM_CATALOG
[
{
"name": "Luma Cloud",
"vendor": "customendpoint",
"apiKey": "${input:lumaCloudApiKey}",
"apiType": "chat-completions",
"url": "https://api.lumaos.cloud/v1"
}
]Use this inside the file opened by VS Code, preserving other providers. Replace ${input:lumaCloudApiKey} with the secret reference generated by your own Add Models flow. Provider-level url requests model discovery; an explicitly configured model instead needs the full /chat/completions URL and its real token limits. Do not use both approaches for the same entry.
Reply with exactly: Luma Cloud connection works.Send this in a new conversation with the Luma Cloud model selected. This is a normal API request and uses the selected key's balance or quota.
Check the connection
- Send a short text request, then check Usage → API Wallet for Wallet usage, or subscription Usage for Builder keys. A populated model list alone does not confirm a successful response.
- Before using an agent on your project, try one read-only file task in a disposable folder. Confirm the tool result and final answer, keeping action approval enabled.
For errors or a request that stops, see troubleshooting. A visible model list alone does not confirm that a chat or editing task can complete.
What to expect
- Current VS Code supports BYOK chat without a Copilot plan. Inline suggestions, semantic search, and embeddings have separate requirements.
- Agent Host BYOK is experimental. This guide does not replace its separate setup.
- The old customOAIModels setting is deprecated. For Responses, use the matching API type and /responses URL.
Troubleshooting VS Code · Chat & Copilot
Custom Endpoint is missing
Check your VS Code version and organization BYOK policy. Do not paste the old github.copilot.chat.customOAIModels setting into a newer setup. If native setup is unavailable, use the separate Continue guide.
The model is visible in Chat but not Agent
Agent mode filters for tool-calling models. Check real model support before enabling toolCalling. A provider display name alone cannot add tool support.
The URL returns 404
Check the field you are editing. A provider-level discovery url uses https://api.lumaos.cloud/v1; a model-level url uses https://api.lumaos.cloud/v1/chat/completions. Do not repeat /v1 or append /models to the model inference URL.
Context usage or generation limits look wrong
Check maxInputTokens and maxOutputTokens. Their sum must not exceed the model's context window. Preserve the generated secret reference when editing these numbers.
401 or invalid API key
Paste the complete Luma Cloud API key again without quotes, spaces, or a Bearer prefix. Confirm that the same key is still active in Dashboard → API. Your dashboard password and Google sign-in are not API keys.
Client documentation
Settings checked on 2026-09-28. These instructions are based on the client’s documentation; installed versions may differ.
