Problem

qwen/qwen3.6-plus model shows as missing: true with null metadata when using the DashScope Coding Plan base URL (https://coding.dashscope.aliyuncs.com/v1), even though the model is explicitly configured in openclaw.json.

Model List Output

{
  "key": "qwen/qwen3.6-plus",
  "name": "qwen/qwen3.6-plus",
  "input": "-",
  "contextWindow": null,
  "local": null,
  "available": null,
  "tags": ["fallback#4", "configured", "missing"],
  "missing": true
}

User Configuration

{
  "providers": {
    "qwen": {
      "baseUrl": "https://coding.dashscope.aliyuncs.com/v1",
      "api": "openai-completions",
      "models": [
        {
          "id": "qwen3.6-plus",
          "name": "qwen3.6-plus",
          "reasoning": false,
          "input": ["text", "image"],
          "cost": {
            "input": 0,
            "output": 0,
            "cacheRead": 0,
            "cacheWrite": 0
          },
          "contextWindow": 1000000,
          "maxTokens": 65536
        }
      ]
    }
  }
}

Root Cause

In the OpenClaw source code, there is filtering logic in dist/models-DBWl8JzO.js:

function isQwenCodingPlanBaseUrl(baseUrl) {
  const hostname = new URL(baseUrl).hostname.toLowerCase();
  return hostname === "coding.dashscope.aliyuncs.com" || 
         hostname === "coding-intl.dashscope.aliyuncs.com";
}

function isQwen36PlusSupportedBaseUrl(baseUrl) {
  return !isQwenCodingPlanBaseUrl(baseUrl);
}

function buildQwenModelCatalogForBaseUrl(baseUrl) {
  return isQwen36PlusSupportedBaseUrl(baseUrl) 
    ? QWEN_MODEL_CATALOG 
    : QWEN_MODEL_CATALOG.filter((model) => model.id !== QWEN_36_PLUS_MODEL_ID);
}

This code explicitly filters out qwen3.6-plus when the base URL is coding.dashscope.aliyuncs.com (the Coding Plan endpoint).

Expected vs Actual

• Expected: qwen3.6-plus should be available on the Coding Plan API, as officially supported by Alibaba Cloud
• Actual: OpenClaw incorrectly filters out this model, causing it to appear in the fallback list with corrupted/incomplete metadata (input: "-", null fields)

Impact

Users with Coding Plan API keys cannot use the qwen3.6-plus model in OpenClaw, even though the model is officially supported by Alibaba Cloud DashScope as of 2025.

Version

OpenClaw 2026.4.22 (00bd2cf)

Suggested Fix

Update isQwen36PlusSupportedBaseUrl() to allow qwen3.6-plus on Coding Plan endpoints (coding.dashscope.aliyuncs.com and coding-intl.dashscope.aliyuncs.com), or remove the filtering entirely if the model is now supported on all DashScope endpoints.

The QWEN_MODEL_CATALOG already includes the model definition - the fix is simply to stop filtering it out for Coding Plan URLs.

Workaround

Switch the base URL to https://api.qwen.com/v1 (standard endpoint) instead of the Coding Plan URL. However, this may not be feasible for users who rely on Coding Plan credits/tiers.