openclaw - 💡(How to fix) Fix Stale suppression: qwen3.6-plus blocked on Coding Plan endpoint despite API support [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75690Fetched 2026-05-02 05:31:41
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Timeline (top)
closed ×1commented ×1

Fix Action

Fix / Workaround

curl -s https://coding-intl.dashscope.aliyuncs.com/v1/chat/completions \\
  -H "Authorization: Bearer \$QWEN_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{"model": "qwen3.6-plus", "messages": [{"role": "user", "content": "Reply with exactly: PATCH_WORKS"}], "max_tokens": 50}'

Returns successfully:

{"model":"qwen3.6-plus","choices":[{"finish_reason":"stop","message":{"role":"assistant","content":"PATCH_WORKS","reasoning_content":"..."}}]}

Code Example

{
  "provider": "qwen",
  "model": "qwen3.6-plus",
  "reason": "qwen3.6-plus is not supported on the Qwen Coding Plan endpoint",
  "when": {
    "baseUrlHosts": ["coding.dashscope.aliyuncs.com", "coding-intl.dashscope.aliyuncs.com"]
  }
}

---

curl -s https://coding-intl.dashscope.aliyuncs.com/v1/chat/completions \\
  -H "Authorization: Bearer \$QWEN_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{"model": "qwen3.6-plus", "messages": [{"role": "user", "content": "Reply with exactly: PATCH_WORKS"}], "max_tokens": 50}'

---

{"model":"qwen3.6-plus","choices":[{"finish_reason":"stop","message":{"role":"assistant","content":"PATCH_WORKS","reasoning_content":"..."}}]}
RAW_BUFFERClick to expand / collapse

Issue

The Qwen provider plugin (openclaw.plugin.json) suppresses qwen3.6-plus on the Coding Plan endpoints, but the API actually supports this model.

Evidence

Suppression entries in ~/.npm-global/lib/node_modules/openclaw/dist/extensions/qwen/openclaw.plugin.json:

{
  "provider": "qwen",
  "model": "qwen3.6-plus",
  "reason": "qwen3.6-plus is not supported on the Qwen Coding Plan endpoint",
  "when": {
    "baseUrlHosts": ["coding.dashscope.aliyuncs.com", "coding-intl.dashscope.aliyuncs.com"]
  }
}

Direct API test confirms the model works:

curl -s https://coding-intl.dashscope.aliyuncs.com/v1/chat/completions \\
  -H "Authorization: Bearer \$QWEN_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{"model": "qwen3.6-plus", "messages": [{"role": "user", "content": "Reply with exactly: PATCH_WORKS"}], "max_tokens": 50}'

Returns successfully:

{"model":"qwen3.6-plus","choices":[{"finish_reason":"stop","message":{"role":"assistant","content":"PATCH_WORKS","reasoning_content":"..."}}]}

Impact

  • Users with Coding Plan API keys cannot use qwen3.6-plus through OpenClaw, despite the API supporting it
  • Forces fallback to qwen3.5-plus or switching to Standard (pay-as-you-go) endpoint
  • The suppression appears to be a relic from when qwen3.6-plus first launched and was not yet available on the Coding Plan endpoint

Suggested Fix

Remove or update the suppressions entries for qwen3.6-plus in openclaw.plugin.json for the Coding Plan base URL hosts. Alternatively, add dynamic model discovery so suppressions stay current automatically (related to #19054).

Environment

  • OpenClaw: 2026.4.29
  • Qwen Provider: bundled qwen plugin
  • Endpoint: coding-intl.dashscope.aliyuncs.com/v1
  • Model: qwen3.6-plus

extent analysis

TL;DR

Remove or update the suppressions entries for qwen3.6-plus in openclaw.plugin.json to enable support for the model on the Coding Plan endpoint.

Guidance

  • Verify the suppression entries in ~/.npm-global/lib/node_modules/openclaw/dist/extensions/qwen/openclaw.plugin.json are causing the issue by checking for the presence of qwen3.6-plus in the model field.
  • Update the openclaw.plugin.json file to remove the suppression entry for qwen3.6-plus or modify the when condition to exclude the Coding Plan endpoint hosts.
  • Test the API again using the curl command provided in the issue to confirm the model works after updating the suppression entries.
  • Consider implementing dynamic model discovery to automatically update suppressions and prevent similar issues in the future.

Example

No code snippet is provided as the issue is related to configuration file updates.

Notes

The suggested fix assumes that the suppression entries in openclaw.plugin.json are the sole cause of the issue. If the problem persists after updating the configuration file, further investigation may be necessary.

Recommendation

Apply workaround: Remove or update the suppressions entries for qwen3.6-plus in openclaw.plugin.json, as this is a straightforward fix that can be implemented immediately to enable support for the model on the Coding Plan endpoint.

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

openclaw - 💡(How to fix) Fix Stale suppression: qwen3.6-plus blocked on Coding Plan endpoint despite API support [1 comments, 2 participants]