Luma Cloud Docs
← All integrations

API setup · Chat Completions

Continue · VS Code & JetBrains + Luma Cloud

Add Luma Cloud to Continue while keeping your other models and editor settings.

Connect with an API key

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.
  • Install Continue in VS Code or your supported JetBrains IDE.

Get an API key and a model ID →

Set up Continue · VS Code & JetBrains

  1. Open the Continue extension

    In VS Code, open Continue from the sidebar. In a JetBrains IDE, open its Continue tool window. Use Continue's configuration dropdown and the gear next to Local Config; this is separate from the editor's own AI settings.

  2. Edit the local model list

    The file is ~/.continue/config.yaml on macOS/Linux and %USERPROFILE%\.continue\config.yaml on Windows. Back it up, then add the model under the existing models list. Do not create a second models key or remove the current name, version, schema, and other model entries.

  3. Save the key locally

    Put LUMA_CLOUD_API_KEY=your-key in ~/.continue/.env, or %USERPROFILE%\.continue\.env on Windows. Keep this file out of Git. Restart the IDE after changing secrets; a shell export alone does not supply secrets to the extension.

  4. Save and select the model

    Replace MODEL_ID_FROM_CATALOG with the exact ID. Save the YAML; Continue reloads model configuration. After adding the secret, restart the IDE, select Local Config, then choose Luma Cloud in Continue's model picker. Begin in Chat mode.

Add this entry to models in config.yaml
models:
  - name: Luma Cloud
    provider: openai
    model: MODEL_ID_FROM_CATALOG
    apiBase: https://api.lumaos.cloud/v1
    apiKey: ${{ secrets.LUMA_CLOUD_API_KEY }}
    useResponsesApi: false
    roles:
      - chat

This selects Chat Completions explicitly. Do not enable useLegacyCompletionsEndpoint. Add edit/apply roles or tool_use only after checking your chosen model's capabilities.

New config.yaml only — when you have no existing configuration
name: Luma Cloud
version: 1.0.0
schema: v1
models:
  - name: Luma Cloud
    provider: openai
    model: MODEL_ID_FROM_CATALOG
    apiBase: https://api.lumaos.cloud/v1
    apiKey: ${{ secrets.LUMA_CLOUD_API_KEY }}
    useResponsesApi: false
    roles:
      - chat

Replace the model placeholder. For an existing file, use the smaller model entry above instead of replacing your configuration.

Secret file — ~/.continue/.env
LUMA_CLOUD_API_KEY=YOUR_LUMA_CLOUD_API_KEY

On Windows use %USERPROFILE%\.continue\.env. Replace the placeholder inside the local file, not in a terminal command. Do not publish, commit, or screenshot the populated file.

First chat request
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

  1. 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.
  2. 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

  • Chat configuration does not configure autocomplete, embeddings, or reranking. Those features need their own supported models.
  • Agent mode needs a model with tool calling; do not force capabilities merely to make it appear.

Troubleshooting Continue · VS Code & JetBrains

The model does not appear

Select Local Config rather than a different cloud configuration. Check YAML indentation and duplicate models keys. Save the file, inspect Continue's configuration error, and reopen the extension.

The key is empty even after a shell export

Continue's IDE extensions do not read your terminal exports. Put LUMA_CLOUD_API_KEY in the global .continue/.env file and restart the IDE. A workspace .env value can override the global value, so check for an older key there.

Chat works but Agent or autocomplete does not

This example only enables the chat role. Agent mode needs supported tool use and appropriate model roles; autocomplete requires a model configured specifically for it. Do not enable capabilities to hide an unsupported-model error.

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.

Model not found or access denied

Copy the exact model ID available to this key from the authenticated catalog. MODEL_ID_FROM_CATALOG is a placeholder, not a model name. Do not substitute a display label or copy an ID from another provider.

Client documentation

Settings checked on 2026-09-28. These instructions are based on the client’s documentation; installed versions may differ.