# Zed + Luma Cloud

Add Luma Cloud as a separate provider for Zed's own AI features.

API connection: Chat Completions. Instructions checked: 2026-09-28. Client capabilities and versions may vary; follow the verification steps below.

This is an API setup guide. SuperGPT desktop installation and sign-in are separate; use a customer API key for the client described here.

## Before you start

- Create a Luma Cloud API key in Dashboard → API and copy a model ID from the authenticated model catalog.

- Use a Zed version with custom OpenAI-compatible providers.

## Setup

1. **Add the provider**
   Run agent: open settings. Under LLM Providers, choose Add Provider and OpenAI-compatible. Name it Luma Cloud.

2. **Enter model details**
   Set the API URL and model ID below. Enter the model's supported context window. Use the provider settings key field; Zed stores the key in the system keychain.

3. **Select capabilities**
   Select the new model. Match tool and image settings to its actual capabilities. For a Responses-only model, set capabilities.chat_completions to false; otherwise use Chat Completions.

4. **Start with the Zed Agent**
   Save the provider and select its model in a new Zed Agent conversation. Do not select an external ACP agent for this check. If you changed an environment-provided key, restart Zed so the local app receives the updated environment.

## Connection fields

- API URL: https://api.lumaos.cloud/v1

- Model ID: MODEL_ID_FROM_CATALOG

- Key storage: Provider settings → system keychain

## Settings template — merge into your existing language_models object

```json
{
  "language_models": {
    "openai_compatible": {
      "luma-cloud": {
        "api_url": "https://api.lumaos.cloud/v1",
        "available_models": [
          {
            "name": "MODEL_ID_FROM_CATALOG",
            "display_name": "Luma Cloud",
            "max_tokens": "REPLACE_WITH_CONTEXT_WINDOW_INTEGER",
            "capabilities": {
              "tools": false,
              "images": false,
              "chat_completions": true
            }
          }
        ]
      }
    }
  }
}
```

This is a template, not a ready-to-save model definition. Replace the model ID and replace the entire quoted context placeholder with the model's numeric context window, without quotes. Enable tools only for a model that supports them before using Zed Agent. Leave your key out of this file; enter it in provider settings on macOS, Windows, or Linux.

## First chat request

```text
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.

## Optional agent check

```text
Read README.md in this test folder and summarize its first paragraph. Do not edit files, run shell commands, or access the network.
```

Create a disposable folder containing a short README.md first. Approve only the file read. Check that a tool result and a final answer both appear.

## Verify

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

## Limits

- Zed's edit prediction has its own configuration. This connection covers model-backed chat, Inline Assistant, and similar Zed features.

- External agents configure their own API connection; they do not inherit this provider automatically.

- Do not place API keys in settings.json. Existing provider environment variables can override saved keys.

## Troubleshooting

### The settings file reports a type error

Replace the quoted context placeholder with an integer. Merge the provider into the existing language_models and openai_compatible objects instead of adding duplicate keys. Using the Add Provider UI avoids manual JSON editing.

### A saved key is ignored

For provider ID luma-cloud, a non-empty LUMA_CLOUD_API_KEY environment variable overrides the saved key. Remove or correct that value and restart Zed. Remote-project model calls still use the local Zed app's credentials.

### An external agent asks you to sign in

This provider config belongs to Zed's own AI features. An ACP agent such as OpenCode uses its own configuration and credentials; follow that agent's guide.

### 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.

## Official client documentation

- [Zed: API access and OpenAI-compatible endpoints](https://zed.dev/docs/ai/use-api-access)