Integration guides ยท 2026-09-22
Qwen3.7-Plus for new integrations instead of Qwen3-Coder-30B
The qwen/qwen3-coder-30b-a3b-instruct identifier carries a retiring status in the catalog; this covers why a new agent/coding integration should start directly with qwen/qwen3.7-plus instead.
Don't ignore the 'Retiring' label on the model page
qwen/qwen3-coder-30b-a3b-instruct's catalog page carries a 'Retiring' status label. That means the row can still be called, but is being phased out on the provider side; starting a new integration with this identifier means building on a foundation that works short-term but needs to be moved medium-term.
In the same family, qwen/qwen3.7-plus carries a broader, current status; it understands image and video input alongside text, positioned as a balanced fit for screen reading, GUI-based agents, coding from visual references, tool use, and long-context assistant workflows.
Which identifier to start a new coding-agent integration with
If you're building an agent/coding integration from scratch, starting directly with qwen/qwen3.7-plus removes the need for a migration project later. Both models support tool calling; qwen3.7-plus also carries a web_search capability and a context window up to 1M tokens, making it possible to process a long repo context in a single request.
If your existing integration already uses the qwen3-coder-30b-a3b-instruct identifier, you don't need to change it urgently; the row still responds. But if you kept the model identifier as a configuration value, moving to qwen3.7-plus is a one-line change, and planning it early is safer than leaving it until the day the row fully retires.
- New integration: start directly with qwen/qwen3.7-plus.
- Existing integration: keep the model identifier as a configuration value and plan the move early.
- qwen3.7-plus additionally carries web_search and a 1M context window.
Verify tool-calling behavior with your own task set
Since the two models come from different base architectures, tool-calling decisions can carry small differences even with the same tool schema and system instruction. Before moving to qwen3.7-plus, testing a handful of coding tasks you commonly run in production with the new identifier and comparing finish_reason and argument accuracy grounds the migration in measurement rather than assumption.
Frequently asked questions
Does the qwen3-coder-30b-a3b-instruct identifier stop working immediately?
No, the 'Retiring' label means the row still responds but is being phased out gradually. There's no immediate outage, but targeting this identifier for new integrations isn't recommended.
Does qwen3.7-plus run at the same price?
No, the two models carry different pricing cards, and qwen3.7-plus has tiered pricing by context length. Compare the two identifiers on the current pricing page before migrating.