Setup guide - From Qwen and Continue docs
Use Qwen in Continue
Continue documents using any OpenAI API compatible provider by setting provider: openai with a custom apiBase in config.yaml. Model Studio documents its OpenAI-compatible base URLs and Qwen model ids, so the two combine directly.
Last verified 2 steps4 official sources
Steps
- Step 1.
Edit Continue's config.yaml and add a model with provider openai and apiBase set to the Model Studio OpenAI-compatible endpoint (pay-as-you-go Singapore shown; replace {WorkspaceId}).
YAMLname: My Config version: 0.0.1 schema: v1 models: - name: Qwen3.7 Plus provider: openai model: qwen3.7-plus apiBase: https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1 apiKey: <YOUR_MODEL_STUDIO_API_KEY> - Step 2.
Coding Plan alternative: use apiBase https://coding-intl.dashscope.aliyuncs.com/v1 with the Coding Plan key.
YAMLapiBase: https://coding-intl.dashscope.aliyuncs.com/v1
Caveats
- Combined setup: Continue's documented OpenAI-compatible apiBase mechanism plus Model Studio's documented base URLs and model ids. There is no Continue-specific Model Studio guide.
- The YAML shape is copied from Continue's OpenAI provider page with Model Studio values substituted.
- Continue defaults to the /responses endpoint only for OpenAI o-series and gpt-5 models; set useResponsesApi: false if a Responses error appears.
- Replace {WorkspaceId}; keys are region- and plan-specific.
More setup guides
Same tool, other providers
Related reading
- Run Qwen3.8-Flash-Next on a Gaming PC With StrataRun Qwen3.8-Flash-Next locally with Strata on a 12 GB GPU: hardware needs, speeds by quant, the license catch, and when the hosted API is the better call.
- Terminal-Universe Turns Agent Traces Into Training EnvironmentsTerminal-Universe, Qwen's paper on rebuilding terminal-agent trajectories into reusable environments, and why agent teams should keep replayable workspaces.
- Qwen3.8-27B vs Opus 4.6 Max: Local Agentic Coding BenchmarksQwen3.8-27B is a 27B dense Apache-2.0 model that beats Opus 4.6 Max on SWE-bench Pro (61.7 vs 53.4). Benchmarks, hardware, cost and when to run it.
- Qwen 3.8 Max Ships: 2.4T MoE, 1M Context, $2/$6 per MTok, Open Weights Next WeekQwen 3.8 Max is a 2.4T-parameter MoE with 95B active, a 1M context window and $2/$6 per million tokens on QwenCloud, with open weights promised next week.
- Qwen-UI-Agent Points at the Next GUI Agent RuntimeQwen-UI-Agent, Alibaba's GUI agent report, reads best as a product spec: mobile, desktop, browser, CLI and DeepSearch combined in one stateful agent runtime.
- $500 RL Fine-Tune of a 9B Open Model Beat GPT-5.6 Sol and Claude Opus 4.8 on Catalog ReviewA $500 GRPO fine-tune of Qwen 3.5 9B beat GPT-5.6 Sol and Opus 4.8 on catalog review, hitting 97% accuracy at a fraction of the cost per listing.
FAQ
How do I use Qwen in Continue?
Continue documents using any OpenAI API compatible provider by setting provider: openai with a custom apiBase in config.yaml. Model Studio documents its OpenAI-compatible base URLs and Qwen model ids, so the two combine directly.
Which Qwen model ids work in Continue?
The official docs read for this guide list qwen3.7-plus, qwen3.6-plus and qwen3.7-max. Requests go to https://{WorkspaceId}.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1.
Is this an official Qwen and Continue setup?
The steps draw on both Qwen's and Continue's docs. It was last checked against 4 official pages on October 17, 2026.
Sources
Last verified against 4 official pages.
- docs.continue.devhttps://docs.continue.dev/customize/model-providers/top-level/openai
- github.comhttps://github.com/continuedev/continue/blob/main/docs/customize/model-providers/top-level/openai.mdx
- alibabacloud.comhttps://www.alibabacloud.com/help/en/model-studio/more-tools
- alibabacloud.comhttps://www.alibabacloud.com/help/en/model-studio/coding-plan
Newsletter
New models, set up the day they ship
One email per week. New model releases, the coding tools that support them and how to wire them up.