Zed Agent setup

Zed includes a native coding Agent that can inspect a project, edit files, and use tools without installing a separate extension. It supports custom OpenAI-compatible providers, making it a good lightweight graphical companion to Lumoswitch on macOS, Linux, and Windows.

Create a Lumoswitch API configuration with OpenAI-compatible output first. Choose a model with reliable native tool calling; chat-only compatibility is not enough for Agent mode.

Choose a setup method

Lumoswitch does not publish an automatic terminal import for Zed. Rewriting a shared JSONC file could discard comments or existing providers, while a shell command cannot safely manage Zed's system-keychain entry across platforms.

Prepare the connection values

Recommended setup in Zed

1. Open the Agent Panel, then open Agent Settings.
2. Under LLM Providers, add an OpenAI Compatible provider.
3. Use lumoswitch as the provider ID and enter {{api_base_url}} as its API URL.
4. Add {{model}} as an available model. Set its context window to the real limit exposed by the selected upstream model.
5. Enter {{access_key}} when Zed asks for the provider API Key. Zed saves it in the system keychain rather than settings.json.
6. Select Lumoswitch · {{model}} from the model picker and test a small file-reading or edit request.

Provider IDs matter: Zed derives the optional environment variable name from the ID. With lumoswitch, the corresponding variable is LUMOSWITCH_API_KEY. Saving the Key through the UI is recommended because graphical applications do not consistently inherit terminal environment variables.

Optional JSONC settings

If the provider editor is unavailable in your Zed version, open agent: open settings from the command palette and merge the following properties into the existing JSONC object:

{
  "language_models": {
    "openai_compatible": {
      "lumoswitch": {
        "api_url": "{{api_base_url}}",
        "available_models": [
          {
            "name": "{{model}}",
            "display_name": "Lumoswitch · {{model}}",
            "max_tokens": 128000,
            "capabilities": {
              "tools": true,
              "images": false,
              "parallel_tool_calls": false,
              "prompt_cache_key": false,
              "chat_completions": true,
              "interleaved_reasoning": false,
            },
          },
        ],
      },
    },
  },
  "agent": {
    "default_model": {
      "provider": "lumoswitch",
      "model": "{{model}}",
    },
  },
}

Replace 128000 and the capability flags with the real model limits. Do not replace the entire settings file: it may contain themes, key bindings, other providers, and comments. Zed stores user settings at ~/.config/zed/settings.json on macOS/Linux and %APPDATA%\Zed\settings.json on Windows.

For a Responses-only Lumoswitch configuration, set chat_completions to false. Keep it true for the OpenAI-compatible Chat Completions setup described on this page.

Remove the setup

1. Open Zed's Agent settings and remove the lumoswitch provider.
2. If the Agent default still points to it, select another model or remove only the matching agent.default_model entry.
3. Clear the saved lumoswitch provider Key through Zed's provider credentials UI.

Do not delete the whole Zed settings file or application data directory. That would remove unrelated editor preferences and may still leave a credential in the system keychain.

Verify and troubleshoot

• A 401 usually means the Key was not saved for the exact lumoswitch provider ID.
• For 404, check for a duplicated /v1 and confirm that {{model}} is the client-facing model name.
• If chat works but edits fail, verify native tool-calling support and the tools capability.
• Remote projects still use the provider configuration and credentials initialized by the local Zed application.

References: Zed API access, Zed Agent, and Zed settings. Last verified: 2026-08-23.