Skip to content
modeldeprecations.dev
Cohere command-r-03-2024

Command R (03-2024) (Cohere)

Deprecated

Yes — Cohere deprecated Command R (03-2024) 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 model that put Cohere on the map for retrieval-augmented generation, with citations and connectors built into the chat API rather than bolted on. Cohere deprecated it on 15 September 2025 and has not published a shutdown date. Under Cohere's own policy the date is assigned at deprecation time; here it was not, so the id is closed to new customers and still answering for existing ones.

The facts

Provider Cohere
Model id command-r-03-2024
Also published as command-r
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 also names command-r-plus-08-2024 and command-a-03-2025. Whichever you pick, the connectors parameter went away in the same announcement, so a RAG integration built on managed connectors needs rewriting rather than repointing.

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

Frequently asked questions

When will Cohere Command R (03-2024) shut down?
Cohere has deprecated Cohere Command R (03-2024) but has not published a shutdown date. Treat it as at risk and plan a migration.
What replaces Cohere Command R (03-2024)?
Cohere recommends Command R (08-2024) (`command-r-08-2024`) as the replacement for Cohere Command R (03-2024). Cohere also names command-r-plus-08-2024 and command-a-03-2025. Whichever you pick, the connectors parameter went away in the same announcement, so a RAG integration built on managed connectors needs rewriting rather than repointing.
Is Cohere Command R (03-2024) still available?
Yes, for now. Cohere Command R (03-2024) 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 R (03-2024) to command-r-08-2024?
Swap the model id in your API call: replace "command-r-03-2024" with "command-r-08-2024". Cohere also names command-r-plus-08-2024 and command-a-03-2025. Whichever you pick, the connectors parameter went away in the same announcement, so a RAG integration built on managed connectors needs rewriting rather than repointing.
Does this apply to command-r too?
Yes. Cohere Command R (03-2024) is also published as `command-r`; that id shares the same lifecycle dates as `command-r-03-2024`.

Sources

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

This page, for machines

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

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

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.