Use any provider in Kilo Code

What yoink writes

The provider goes under provider.<id>, and the default under the top-level model key. For an OpenRouter key saved as openrouter and connected with --default z-ai/glm-4.7 (key redacted):

{
  "provider": {
    "openrouter": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "OpenRouter",
      "options": {
        "baseURL": "https://openrouter.ai/api/v1",
        "apiKey": "<your key>"
      },
      "models": {
        "z-ai/glm-4.7": {
          "name": "GLM-4.7",
          "tool_call": true,
          "reasoning": true,
          "limit": { "context": 204800, "output": 131072 }
        }
      }
    }
  },
  "model": "openrouter/z-ai/glm-4.7"
}

The npm package follows the protocol: @ai-sdk/openai-compatible for OpenAI Chat, @ai-sdk/anthropic for Anthropic Messages, @ai-sdk/openai for OpenAI Responses. The opencode page has the full table and explains which model keys yoink owns.

Filling in the limits Kilo cannot detect

Kilo's own OpenAI-compatible provider guide sets a custom provider up in the Settings UI, and sends you to the config file for token limits and tool calling. yoink writes those for you: limit.context and limit.output come from models.dev when it knows the model, with fallbacks of 128,000 and 32,000 tokens when it does not, and every model gets tool_call: true.

How Kilo differs from opencode in yoink

Both files are edited in place, so comments in kilo.jsonc and your formatting survive a connect, a re-sync or a disconnect. When both kilo.json and kilo.jsonc exist, yoink edits kilo.json.

Which providers work

Kilo Code takes all three protocols, preferring OpenAI Chat, then Anthropic Messages, then OpenAI Responses. Every preset can reach it, ollama included, and so can any custom URL that answers one probe.

yoink connect openrouter --to kilo --default z-ai/glm-4.7
yoink connect openrouter --to kilo,opencode
yoink connect ollama --to kilo

Connecting the same provider to Kilo and opencode in one command is a good fit: both get the same entry, and yoink models <name> or a rotated key updates both.

Set the default model

--default <model> writes "model": "<provider>/<model>". Leave it out to keep Kilo's current default. When you disconnect, yoink clears model and small_model only if they point at that provider.

Backups and disconnect

The first change to an existing kilo.json copies it to kilo.json.yoink.bak, once (see Backups). yoink disconnect openrouter --from kilo removes provider.openrouter and prunes the provider object if it ends up empty.

Gotchas

• Literal key. yoink writes the key as a literal options.apiKey. Kilo entries that use {env:VAR} or {file:...} are skipped by yoink import, because yoink cannot sync a key it does not hold.
• Restart Kilo Code after a change so it reloads its config.

FAQ