Use DeepSeek V4.1 Flash and GLM 5.3 Flash in Kilo Code

Point Kilo Code at OpenScale with one tested setup. Your existing Kilo Code configuration stays yours.

Tested live with the Kilo Code 7.8.8 CLI: file edits, shell, reasoning replay and streaming. The VS Code extension reads the same file.

Quick start

The fastest way to try it. Replace YOUR_OPENSCALE_API_KEY with your key and run it yourself; do not paste the key into an agent conversation. Paste this into your terminal.

terminal
export KILO_CONFIG_CONTENT='{"provider":{"openscale":{"npm":"@ai-sdk/openai-compatible","options":{"baseURL":"https://api.openscale.so/v1","apiKey":"YOUR_OPENSCALE_API_KEY"},"models":{"deepseek/deepseek-v4.1-flash":{"tool_call":true,"reasoning":true,"attachment":true,"interleaved":{"field":"reasoning_content"},"limit":{"context":1048568,"output":384000}},"z-ai/glm-5.3-flash":{"tool_call":true,"reasoning":true,"attachment":true,"interleaved":{"field":"reasoning_content"},"limit":{"context":1048576,"output":131072}}}}}}'
kilo -m openscale/deepseek/deepseek-v4.1-flash
Protocol
Chat Completions
Base URL
https://api.openscale.so/v1

Keep it in Kilo Code's config

Uses the provider schema of Kilo Code 7.x, shared by the kilo CLI and the VS Code extension. Check kilo --version first.

  1. Merge the provider configuration

    Default path: ~/.config/kilo/kilo.json.

    Merge only provider.openscale into ~/.config/kilo/kilo.json or kilo.jsonc. Respect KILO_CONFIG and project config. In the VS Code extension the same provider can be added under Settings, Providers, Custom provider with Provider API OpenAI Compatible; token limits are only set in the file.

    This is a merge fragment, not a replacement for an existing file. Model metadata is generated from OpenScale's catalog; prices are estimates in USD per million tokens, not an account balance or billing receipt.

    Download config fragment
    ~/.config/kilo/kilo.json
    {
      "$schema": "https://app.kilo.ai/config.json",
      "provider": {
        "openscale": {
          "npm": "@ai-sdk/openai-compatible",
          "name": "OpenScale",
          "env": [
            "OPENSCALE_API_KEY"
          ],
          "options": {
            "baseURL": "https://api.openscale.so/v1"
          },
          "models": {
            "deepseek/deepseek-v4.1-flash": {
              "name": "DeepSeek V4.1 Flash",
              "tool_call": true,
              "reasoning": true,
              "attachment": true,
              "interleaved": {
                "field": "reasoning_content"
              },
              "modalities": {
                "input": [
                  "text",
                  "image"
                ],
                "output": [
                  "text"
                ]
              },
              "limit": {
                "context": 1048568,
                "output": 384000
              },
              "cost": {
                "input": 0.06,
                "output": 0.24,
                "cache_read": 0.003
              }
            },
            "z-ai/glm-5.3-flash": {
              "name": "GLM 5.3 Flash",
              "tool_call": true,
              "reasoning": true,
              "attachment": true,
              "interleaved": {
                "field": "reasoning_content"
              },
              "modalities": {
                "input": [
                  "text",
                  "image"
                ],
                "output": [
                  "text"
                ]
              },
              "limit": {
                "context": 1048576,
                "output": 131072
              },
              "cost": {
                "input": 0.12,
                "output": 0.4,
                "cache_read": 0.024
              }
            }
          }
        }
      }
    }
    
  2. Authenticate locally

    The provider reads OPENSCALE_API_KEY from the environment that launches Kilo. You can also put the key in provider.openscale.options.apiKey in the global config.

    Never paste your key into an agent conversation.

  3. Select and verify

    Reopen Kilo after saving the configuration.

    Run kilo with -m openscale/deepseek/deepseek-v4.1-flash, set "model": "openscale/deepseek/deepseek-v4.1-flash" in kilo.json, or pick it with /models.

    Official Kilo Code documentation

Models and prices

Prices are USD per 1M tokens. You pay only for the tokens you use, and new accounts get free credit to try it.

ModelInputCached inputOutput
DeepSeek V4.1 Flashdeepseek/deepseek-v4.1-flash$0.06$0.003$0.24
GLM 5.3 Flashz-ai/glm-5.3-flash$0.12$0.024$0.40

The full catalog, with context windows and limits, is at api.openscale.so/v1/models.

Let your agent set it up

An agent that can fetch URLs and edit local files can do the setup for you. Paste this prompt into it.

prompt
Read https://openscale.so/setup.md and follow the Kilo Code recipe to configure OpenScale on this machine. Preserve my existing configuration and verify the connection. Guide me through entering my API key locally if needed.
  1. Confirm the requested agent and inspect its installed version and active configuration location. Read only the relevant settings; do not dump credential stores or unrelated environment variables. If the agent is not installed, link its official installation instructions and let the user choose installation.
  2. Read the matching recipe and its linked configuration. If the installed schema differs, consult the linked official docs for that version. Do not guess, silently upgrade, or apply a different version's schema.
  3. Back up any file you will edit with a unique timestamp and its existing permissions. Backups may contain secrets: keep them local and private. Merge only the OpenScale provider block with a format-aware editor. Preserve JSONC/JSON5/YAML/TOML comments, other providers, defaults, profiles, secrets and unrelated settings. Never overwrite the full file with a downloaded snippet. On reruns update the same provider, without duplicate keys. Preserve existing OpenScale customizations unless they conflict with the requested setup.
  4. Ask the user to create an account at https://openscale.so/signup?utm_source=agent_setup&utm_medium=agent, create an API key at https://app.openscale.so/app/keys, and ensure credits are available. Let them enter the key in the agent's local credential flow or private environment configuration. Never request the key in chat, print it, put it in shell history, commit it, or send it to any endpoint except https://api.openscale.so. Reuse an existing working credential without displaying it.
  5. Validate configuration syntax and use the agent's supported reload procedure. Select an OpenScale model for the test session; preserve the previous default unless the user explicitly requests changing it. Keep separate vision, audio and auxiliary provider settings unless the user asks to move them too.
  6. Fetch https://api.openscale.so/v1/models without authentication to confirm the chosen model ID exists. That checks discovery, not credentials or inference. Through the configured agent, send one short prompt: “Reply with OK.” Confirm the response and selected provider/model. For coding agents, also ask it to use one harmless read-only tool (for example, report the current directory) and answer after the tool result. Do not claim tool support from a text-only test. This small test uses account credits; do not run repeated benchmarks.
  7. Report the agent version, changed paths (no secrets), selected model, discovery result, inference result and tool result separately. If credentials or a restart are pending, say “configuration saved; connection not yet verified.” Do not report success from merely writing a file.

Troubleshooting and undo

  • Missing models: check active profile, provider filters, model allowlists and overrides before changing unrelated settings.
  • 401: re-enter the key locally. 402: check account credits. 404: check the base URL for the recipe's protocol and the exact live model ID. 429: respect Retry-After and retry with backoff. Do not loop indefinitely.
  • Streaming or tool errors: record the agent version and a redacted error, and check that the agent uses the protocol and base URL its recipe states. Do not switch protocols on your own; each recipe names the one that was tested.
  • Undo: remove only the OpenScale provider entries added by this setup and restore any selection changed for testing. If restoring a backup, first ensure it will not discard subsequent edits. Remove only credentials created for this setup using the agent's supported local auth flow.

Questions

Which models can I use in Kilo Code with OpenScale?

This guide sets up DeepSeek V4.1 Flash (deepseek/deepseek-v4.1-flash) and GLM 5.3 Flash (z-ai/glm-5.3-flash). Every model in the catalog is listed at https://api.openscale.so/v1/models.

How much does Kilo Code cost with OpenScale?

You pay per token, with no subscription needed. DeepSeek V4.1 Flash: $0.06 input, $0.003 cached input and $0.24 output per 1M tokens. GLM 5.3 Flash: $0.12 input, $0.024 cached input and $0.40 output per 1M tokens. New accounts get free credit to try it.

Which API does Kilo Code use with OpenScale?

Chat Completions, at the base URL https://api.openscale.so/v1. One OpenScale API key works for every agent and protocol.

Has this Kilo Code setup been tested?

Tested live with the Kilo Code 7.8.8 CLI: file edits, shell, reasoning replay and streaming. The VS Code extension reads the same file.

How do I undo the setup?

Remove only the OpenScale provider entries added by this setup and restore any selection changed for testing. If restoring a backup, first ensure it will not discard subsequent edits. Remove only credentials created for this setup using the agent's supported local auth flow.

Guides for other agents

All agentsAPI referenceThis guide as Markdown