Skip to content
modeldeprecations.dev
Calendar Changelog API GitHub

Providers

Amazon Anthropic Cohere DeepSeek Google MiniMax Mistral Moonshot AI OpenAI Qwen xAI Xiaomi MiMo Z.ai

Providers

Amazon 8 Anthropic 31 Cohere 35 DeepSeek 5 Google 34 MiniMax 17 Mistral 53 Moonshot AI 18 OpenAI 106 Qwen 26 xAI 26 Xiaomi MiMo 4 Z.ai 22
Qwen qwen3-coder-plus

Qwen3 Coder Plus (Qwen)

Deprecated Shuts down in 68 days

Yes — Qwen deprecated Qwen3 Coder Plus and shuts it down on October 10, 2026 (in 68 days). The recommended replacement is Qwen3.7 Plus.

Alibaba's dedicated coding model, popular well outside China because the open Qwen3-Coder weights made it easy to try before paying for the hosted id. Its retirement folds coding back into the general Plus tier, the same consolidation Mistral and Moonshot made in the same period.

The facts

Provider Qwen
Model id qwen3-coder-plus
Released —
Deprecated date not published
Shutdown October 10, 2026 · in 68 days
Status Deprecated
Last verified August 3, 2026

What to use instead

Qwen Qwen3.7 Plus qwen3.7-plus Provider-recommended Active

What parameters qwen3.7-plus accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them. 

- "model": "qwen3-coder-plus"
+ "model": "qwen3.7-plus"

Frequently asked questions

When will Qwen Qwen3 Coder Plus shut down?
Qwen Qwen3 Coder Plus is scheduled to shut down on October 10, 2026, in 68 days.
What replaces Qwen Qwen3 Coder Plus?
Qwen recommends Qwen3.7 Plus (`qwen3.7-plus`) as the replacement for Qwen Qwen3 Coder Plus.
Is Qwen Qwen3 Coder Plus still available?
Yes, for now. Qwen Qwen3 Coder Plus is deprecated but still answers requests until October 10, 2026. Deprecated models get no further updates and are the first to lose capacity.
How do I migrate from Qwen Qwen3 Coder Plus to qwen3.7-plus?
Swap the model id in your API call: replace "qwen3-coder-plus" with "qwen3.7-plus". Keep the rest of the request the same, then re-check the parameters the new model accepts before you ship.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

JSON Markdown Badge JSON

Drop the badge in a README so it turns red the day this model is retired:

[![qwen3-coder-plus](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/qwen/qwen3-coder-plus.json)](https://modeldeprecations.dev/qwen/qwen3-coder-plus)

Other Qwen models

All Qwen deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.