AGENT INTEGRATIONS

OpenCode

Configure both DeepSeek preview IDs in one custom provider.

On this pageCurrent availabilityInstall and check your versionPrepare your keySave the providerStart OpenCodeSwitch modelsChoose reasoning effortVerify your first requestTroubleshoot and restoreReference
Preview connection · Configuration examples only. Check service availability before using a real key. Example only: https://api.dssub.invalid/v1 is not a live endpoint.

Current availability#

DSSUB is a design preview. These are complete configuration references, not a live connection: api.dssub.invalid is intentionally non-routable. No real account, key, payment or inference service is connected. Replace the endpoint and use an authorized key only after DSSUB publishes verified connection details. Client versions and live tool compatibility remain unverified.

Install and check your version#

Install from OpenCode and run opencode --version. Current documentation uses providers, package and settings. The ZIP also contains a separate opencode-v1.json for older clients using provider, npm and options. Use the schema for your installed version; do not combine both formats.

Prepare your key#

When a real endpoint is available, supply its authorized key in the same terminal that starts the tool. The following value is a placeholder.

macOS or Linux

sh
export DSSUB_API_KEY="YOUR_DSSUB_API_KEY"

Windows PowerShell

powershell
$env:DSSUB_API_KEY = "YOUR_DSSUB_API_KEY"

Do not add a real key to a shared project or downloaded template. Desktop applications may not inherit terminal environment variables; use their supported credential setup.

Save the provider#

For the current format, save the following as opencode.json in your test project or merge it into your existing configuration. Both model IDs are included.

json
{
  "$schema": "https://opencode.ai/config.json",
  "model": "dssub/deepseek-flash",
  "providers": {
    "dssub": {
      "name": "DSSUB preview",
      "env": [
        "DSSUB_API_KEY"
      ],
      "package": "@opencode/ai/providers/openai-compatible",
      "settings": {
        "baseURL": "https://api.dssub.invalid/v1"
      },
      "models": {
        "deepseek-flash": {
          "name": "DeepSeek V4.1 Flash"
        },
        "deepseek-v4-pro": {
          "name": "DeepSeek V4 Pro"
        }
      }
    }
  }
}

For a V1 client, use the supplied opencode-v1.json as opencode.json instead. The credential comes from DSSUB_API_KEY, not a key embedded in the file.

Start OpenCode#

sh
opencode --model dssub/deepseek-flash

Switch models#

Enter /models and select the DSSUB provider, or start a new session with opencode --model dssub/deepseek-v4-pro. If it is missing, verify the configuration path and version-specific schema before changing credentials.

Choose reasoning effort#

OpenCode can expose model variants where the provider and model define them. No DSSUB reasoning variants are verified in this template. Use the default until a tested provider configuration publishes supported levels; do not assume a variant selector guarantees backend support.

Verify your first request#

After a live connection is published, start a new session in a small test project. First ask for a short text reply. Then ask the tool to read README.md and summarize it without modifying files. Confirm the selected provider and model, then match the request in Usage. Check tool results, streaming completion and billed tokens separately. The current sample dashboard cannot verify a real request.

Troubleshoot and restore#

A DNS failure for api.dssub.invalid is expected in this preview. For a real connection, check the exact endpoint, API format, model ID and credential. A 401 concerns authentication; a 404 may concern a path or model; a 429 may concern a quota or rate limit. See troubleshooting.

Back up configuration before editing, merge only DSSUB fields, and retain your existing providers and permissions. To revert, select your previous provider and restore only the fields you changed. Stop and restart the tool after changing its startup environment.

Reference#

Official provider configuration and V1 migration, reviewed November 16, 2026.

Guide updated November 5, 2026 · All tutorials