openclaw - 💡(How to fix) Fix Qwen: qwen3.6-plus is blocked on Coding Plan Pro endpoint despite being officially supported

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Root Cause

Root cause: In extensions/qwen/models.ts (compiled to dist/models-*.js), the function isQwen36PlusSupportedBaseUrl checks a whitelist of base URLs. The Coding Plan endpoint is not on this whitelist, so qwen3.6-plus is silently filtered out — even though the upstream API fully supports it. Additionally, suppressBuiltInModel in extensions/qwen/index.js blocks the model at runtime.

Fix Action

Fix / Workaround

Auswirkung: Coding-Plan-Pro-Nutzer können das offiziell empfohlene Modell nicht verwenden, obwohl sie dafür bezahlen. Sie müssen die dist-Dateien manuell patchen (zwei Stellen ändern), und dieser Patch muss nach jedem npm update openclaw wiederholt werden.

Bitte: Einer dieser PRs sollte gemerged werden, damit Coding-Plan-Nutzer qwen3.6-plus ohne manuelle Patches verwenden können.

Impact: Coding Plan Pro users cannot use the officially recommended model they are paying for. The workaround is to manually patch two lines in the dist files, and this patch must be reapplied after every npm update openclaw.

RAW_BUFFERClick to expand / collapse

Problem

OpenClaw hardcodes a filter that blocks qwen3.6-plus when the configured Qwen provider uses the Coding Plan endpoint (https://coding.dashscope.aliyuncs.com/v1), even though Alibaba Cloud officially includes qwen3.6-plus as the recommended flagship model for the Coding Plan Pro subscription.


🇩🇪 Deutsch

Problem: OpenClaw filtert qwen3.6-plus hartcodiert heraus, wenn der Qwen-Provider den Coding-Plan-Endpunkt (https://coding.dashscope.aliyuncs.com/v1) verwendet.

Hintergrund: Der Alibaba Cloud Coding Plan Pro (¥200/Monat) enthält qwen3.6-plus als empfohlenes Flaggschiff-Modell mit Bildverständnis und 1M Token Kontextfenster. Der Lite-Plan wurde am 20. März 2026 eingestellt; seitdem ist Pro die einzige Option. Offizielle Dokumentation: https://help.aliyun.com/zh/model-studio/coding-plan

Ursache: In extensions/qwen/models.ts (bzw. der kompilierten dist/models-*.js) prüft die Funktion isQwen36PlusSupportedBaseUrl eine Whitelist von Base URLs. Der Coding-Plan-Endpunkt ist nicht enthalten, daher wird qwen3.6-plus stillschweigend herausgefiltert — obwohl der Upstream-Provider das Modell vollständig unterstützt. Zusätzlich blockiert suppressBuiltInModel in extensions/qwen/index.js das Modell zur Laufzeit.

Auswirkung: Coding-Plan-Pro-Nutzer können das offiziell empfohlene Modell nicht verwenden, obwohl sie dafür bezahlen. Sie müssen die dist-Dateien manuell patchen (zwei Stellen ändern), und dieser Patch muss nach jedem npm update openclaw wiederholt werden.

Bestehende PRs: Zwei PRs warten auf Merge:

  • #66367 — Entfernt die Filter- und Suppress-Logik vollständig
  • #63987 — Ermöglicht Opt-in für qwen3.6-plus auf Coding-Plan-Endpunkten

Bitte: Einer dieser PRs sollte gemerged werden, damit Coding-Plan-Nutzer qwen3.6-plus ohne manuelle Patches verwenden können.


🇬🇧 English

Problem: OpenClaw hardcodes a filter that blocks qwen3.6-plus when the Qwen provider is configured with the Coding Plan endpoint (https://coding.dashscope.aliyuncs.com/v1).

Background: Alibaba Cloud's Coding Plan Pro (¥200/month) includes qwen3.6-plus as the recommended flagship model, with image understanding and a 1M token context window. The Lite plan was discontinued on March 20, 2026; Pro is now the only option. Official docs: https://help.aliyun.com/zh/model-studio/coding-plan

Root cause: In extensions/qwen/models.ts (compiled to dist/models-*.js), the function isQwen36PlusSupportedBaseUrl checks a whitelist of base URLs. The Coding Plan endpoint is not on this whitelist, so qwen3.6-plus is silently filtered out — even though the upstream API fully supports it. Additionally, suppressBuiltInModel in extensions/qwen/index.js blocks the model at runtime.

Impact: Coding Plan Pro users cannot use the officially recommended model they are paying for. The workaround is to manually patch two lines in the dist files, and this patch must be reapplied after every npm update openclaw.

Existing PRs: Two PRs are waiting to be merged:

  • #66367 — Removes the filtering and suppression logic entirely
  • #63987 — Allows opt-in for qwen3.6-plus on Coding Plan endpoints

Request: Please merge one of these PRs so Coding Plan users can use qwen3.6-plus without manual patches.


🇨🇳 中文

问题: OpenClaw 在代码中硬编码了过滤逻辑,当 Qwen 提供商配置为 Coding Plan 端点(https://coding.dashscope.aliyuncs.com/v1)时,qwen3.6-plus 模型被静默过滤掉。

背景: 阿里云百炼 Coding Plan Pro(¥200/月)将 qwen3.6-plus 作为推荐旗舰模型,支持图片理解和 100 万 token 上下文窗口。Lite 套餐已于 2026 年 3 月 20 日停止新购,Pro 是目前唯一可选方案。官方文档:https://help.aliyun.com/zh/model-studio/coding-plan

根因:extensions/qwen/models.ts(编译后为 dist/models-*.js)中,isQwen36PlusSupportedBaseUrl 函数通过白名单判断哪些端点支持 qwen3.6-plus。Coding Plan 端点不在白名单中,因此该模型被静默过滤——尽管上游 API 完全支持。此外,extensions/qwen/index.js 中的 suppressBuiltInModel 在运行时也会屏蔽该模型。

影响: Coding Plan Pro 用户无法使用官方推荐且已付费的模型。目前的 workaround 是手动修改 dist 文件中的两处代码,且每次 npm update openclaw 后都需要重新打补丁。

已有 PR: 两个 PR 等待合并:

  • #66367 — 完全移除过滤和屏蔽逻辑
  • #63987 — 允许 Coding Plan 端点 opt-in qwen3.6-plus

诉求: 请合并其中一个 PR,让 Coding Plan 用户无需手动修改源码即可使用 qwen3.6-plus

extent analysis

TL;DR

Merge one of the existing PRs (#66367 or #63987) to remove the hardcoded filter that blocks qwen3.6-plus for Coding Plan Pro users.

Guidance

  • Review the two existing PRs (#66367 and #63987) to understand the proposed changes and their implications.
  • Consider the trade-offs between removing the filtering and suppression logic entirely (PR #66367) versus allowing opt-in for qwen3.6-plus on Coding Plan endpoints (PR #63987).
  • Evaluate the potential impact of merging one of these PRs on the overall functionality and user experience of OpenClaw.
  • Test the changes thoroughly to ensure that qwen3.6-plus is properly supported for Coding Plan Pro users after merging the PR.

Example

No code snippet is provided as the issue is more related to the merge of existing PRs rather than a specific code change.

Notes

The solution relies on the merge of one of the existing PRs, which may have different implications depending on the chosen approach. It's essential to carefully review and test the changes before merging.

Recommendation

Apply workaround by merging PR #66367, as it completely removes the filtering and suppression logic, providing a more straightforward solution for Coding Plan Pro users to use qwen3.6-plus.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING