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
Cohere command-light

Command Light (Cohere)

Deprecated

Yes — Cohere deprecated Command Light on September 15, 2025 but has not published a shutdown date. It still answers requests today. The recommended replacement is Command R (08-2024).

The cheap, small sibling of the original Command, and for a long time the budget option for classification and short generation on Cohere. Deprecated 15 September 2025 with no shutdown date. Cohere named no small replacement for it in that notice - command-r7b-12-2024 is the closest thing in the current range.

The facts

Provider Cohere
Model id command-light
Released —
Deprecated September 15, 2025
Shutdown not published
Status Deprecated
Last verified August 3, 2026

What to use instead

Cohere Command R (08-2024) command-r-08-2024 Provider-recommended Active

Cohere's named alternatives are all considerably larger than command-light was. If cost per token was why you were on this id, command-r7b-12-2024 is the closer match even though the notice does not mention it.

What parameters command-r-08-2024 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": "command-light"
+ "model": "command-r-08-2024"

Frequently asked questions

When will Cohere Command Light shut down?
Cohere has deprecated Cohere Command Light but has not published a shutdown date. Treat it as at risk and plan a migration.
What replaces Cohere Command Light?
Cohere recommends Command R (08-2024) (`command-r-08-2024`) as the replacement for Cohere Command Light. Cohere's named alternatives are all considerably larger than command-light was. If cost per token was why you were on this id, command-r7b-12-2024 is the closer match even though the notice does not mention it.
Is Cohere Command Light still available?
Yes, for now. Cohere Command Light is deprecated but still answers requests. Deprecated models get no further updates and are the first to lose capacity.
How do I migrate from Cohere Command Light to command-r-08-2024?
Swap the model id in your API call: replace "command-light" with "command-r-08-2024". Cohere's named alternatives are all considerably larger than command-light was. If cost per token was why you were on this id, command-r7b-12-2024 is the closer match even though the notice does not mention it.

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:

[![command-light](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/cohere/command-light.json)](https://modeldeprecations.dev/cohere/command-light)

Other Cohere models

All Cohere 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.