From 3c0eac31f1abba0fac0f3df430b382bf72f455ca Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Tue, 28 Apr 2026 03:40:20 -0700 Subject: [PATCH] docs(providers/qwen): note explicit qwen3.6-plus opt-in on Coding Plan For 058b57867e: docs/providers/qwen.md "Qwen 3.6 Plus availability" accordion now records that the bundled catalog still does not advertise `qwen3.6-plus` on Coding Plan endpoints, but explicitly configured `models.providers.qwen.models` entries for that model are honored on Coding Plan baseUrls so subscribers whose plan enables it can opt in. The upstream API still decides whether the call succeeds. --- docs/providers/qwen.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/providers/qwen.md b/docs/providers/qwen.md index 8d1ca6b8ced..869de6575df 100644 --- a/docs/providers/qwen.md +++ b/docs/providers/qwen.md @@ -235,6 +235,12 @@ See [Video Generation](/tools/video-generation) for shared tool parameters, prov `qwen3.6-plus`, switch to Standard (pay-as-you-go) instead of the Coding Plan endpoint/key pair. + OpenClaw's bundled Qwen catalog does not advertise `qwen3.6-plus` on Coding + Plan endpoints, but explicitly configured `qwen/qwen3.6-plus` entries under + `models.providers.qwen.models` are honored on Coding Plan baseUrls so you + can opt that model in if Aliyun enables it on your subscription. The + upstream API still decides whether the call succeeds. +