openclaw - 💡(How to fix) Fix qwen3.6-plus model shows as 'missing' when using DashScope Coding Plan base URL [1 participants]

Problem

model shows as with null metadata when using the DashScope Coding Plan base URL (), even though the model is explicitly configured in .

Model List Output

User Configuration

Root Cause

In the OpenClaw source code (), there is filtering logic:

This code **explicitly filters out ** when the base URL is (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

Impact

Users with Coding Plan API keys cannot use the model in OpenClaw, even though the model is officially supported by Alibaba Cloud.

Version

OpenClaw 2026.4.22 (00bd2cf)

Suggested Fix

Update to allow on Coding Plan endpoints, or remove the filtering entirely if the model is now supported.

Alternatively, the model catalog should be updated to reflect current Alibaba Cloud DashScope capabilities.

Workaround

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