Use any provider in Zed

What yoink writes

The block goes under openai_compatible or anthropic_compatible, keyed by the profile id. Here is the OpenRouter preset with --default z-ai/glm-4.7:

{
  "language_models": {
    "openai_compatible": {
      "openrouter": {
        "api_url": "https://openrouter.ai/api/v1",
        "available_models": [
          {
            "name": "z-ai/glm-4.7",
            "display_name": "GLM-4.7",
            "max_tokens": 204800,
            "max_output_tokens": 131072,
            "capabilities": {
              "tools": true,
              "parallel_tool_calls": false,
              "prompt_cache_key": false,
              "images": false,
              "chat_completions": true
            }
          }
        ]
      }
    }
  },
  "agent": {
    "default_model": { "provider": "openrouter", "model": "z-ai/glm-4.7" }
  }
}

max_tokens is the context window and max_output_tokens the output limit, both from the model data yoink keeps for the provider. In capabilities, yoink always sets images and chat_completions. It seeds tools: true, parallel_tool_calls: false and prompt_cache_key: false only the first time, so if you flip one of those three by hand, your value stays.

Three shapes, one per protocol

Zed accepts all three protocols, in the order Chat, Responses, Anthropic. Zed's API access docs describe both sections yoink uses.

Because Chat comes first, every preset except a Responses-only gateway lands as Chat, openai included. A custom gateway that answers only /responses gets the chat_completions: false shape. If a provider's endpoints change and it moves from one section to the other, yoink deletes the old block so the provider never appears twice.

Setting the key

yoink prints the variable name after connecting. It is the profile id in upper case, with every run of characters other than letters and digits turned into _, plus _API_KEY:

yoink connect openrouter --to zed --default z-ai/glm-4.7
export OPENROUTER_API_KEY="<your key>"

A provider saved as fuse reads FUSE_API_KEY. Zed has to inherit the variable, so launch it from a shell that exports it, or paste the key into the provider in Zed's agent settings instead. This step is why Zed is marked experimental: yoink cannot put the key where Zed reads it.

Paths and detection

• Linux and macOS: ~/.config/zed/settings.json, or under $XDG_CONFIG_HOME/zed.
• Windows: %APPDATA%\Zed\settings.json.

yoink counts Zed as installed when zed or zeditor is on your PATH, /Applications/Zed.app or /Applications/Zed Preview.app exists, or the config folder does.

Disconnect and backups

yoink disconnect openrouter --from zed removes the openrouter block from whichever section holds it, clears agent.default_model only when it names openrouter, and drops any section left empty. The first write keeps the original as settings.json.yoink.bak.

FAQ