SunsetDiff

Claude Opus 4.5 will not shut down before November 24, 2026

Anthropic's deprecations page lists claude-opus-4-5-20251101 as Active, with Deprecated N/A and tentative retirement not sooner than 2026-11-24. That cell is the earliest possible shutdown, not the day the model stops. The deprecation history does not name a replacement. The Opus 4.5 page says: "Although Claude Opus 4.5 is still available, you should consider migrating to Claude Opus 5.5." That sentence is not a deprecations-history row, so no replacement is stored. The same deprecations page says: "The dates on this page apply to Anthropic-operated platforms: the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Microsoft Foundry." It also says: "Partner-operated platforms, Amazon Bedrock and Claude Models on Google Cloud (Google managed), set their own retirement schedules, so a model's lifecycle status and dates can differ." GitHub Copilot lists Claude Opus 4.5 on 2026-09-01. After a real retirement, the deprecations page says requests fail. It does not print an HTTP status or an error sentence.

Last reviewed . Publisher: SunsetDiff.

Steps

  1. Read November 24, 2026 as a floor. The status table says Active and Deprecated N/A. The retirement cell says not sooner than November 24, 2026. Do not remove the id on that day. The deprecations page says: "Anthropic notifies customers with active deployments for models with upcoming retirements, providing at least 60 days' notice before model retirement for publicly released models." A fixed retirement date would be a Deprecated row with a retirement date. This row is not that.
  2. Find the ids in code and config. Search for claude-opus-4-5-20251101, the alias claude-opus-4-5, the Bedrock id anthropic.claude-opus-4-5-20251101-v1:0, and the Google-managed id claude-opus-4-5@20251101. Check source files, env files, YAML, TOML, and JSON. The Claude Console usage export lists calls by API key and model. The scan page skips active models, so this id is not on that list.
  3. Open the current models list before you pick an id. The deprecations history does not name a replacement. The models overview is the current list. The Opus 4.5 page says to consider Claude Opus 5.5 and links its migration guide. Other Active Opus ids on the deprecations table are still current too. This guide does not pick one for you.
  4. If you call claude-opus-5-5, drop the settings it rejects. The Opus 5.5 migration guide says: "Where an item says a setting is rejected, the API returns a 400 error." Remove temperature, top_p, and top_k. Remove thinking type enabled and thinking type disabled. Do not end messages with an assistant prefill. Do not send tool_choice type tool or any. Send one test call with a prompt you use now. November 24, 2026 is not that test deadline.

What November 24, 2026 means

The dataset has 1 Anthropic id with shutdown date 2026-11-24 and kind not_before: claude-opus-4-5-20251101. The deprecations status table says Active, Deprecated N/A, tentative retirement not sooner than November 24, 2026. The page defines Active as: "The model is fully supported and recommended for use."

Not sooner than November 24, 2026 is the earliest possible shutdown. It is not a promise that the model stops that day, and it is not a deprecation date. SunsetDiff stores shutdown_date_kind not_before for that cell. The deprecations page says: "Anthropic notifies customers with active deployments for models with upcoming retirements, providing at least 60 days' notice before model retirement for publicly released models."

The Opus 4.5 page labels the model Legacy and says it was released November 24, 2025. Its availability table lists status Active (legacy) and retirement Not sooner than November 24, 2026. The stored status stays active because the scraper reads the deprecations status table, which says Active. A refresh does not copy the Legacy banner onto the row.

/shutdowns/anthropic-2026-11-24/ lists this id. The date on that page is the not_before floor from the deprecations table, not an exact shutdown day. A shutdown batch usually needs at least 3 model records that share one provider and one exact shutdown date. This page is published for the one stored floor.

Anthropic model id in the dataset with shutdown date 2026-11-24 and kind not_before.
Model idStatusDate on the deprecations tableRecommended replacement
claude-opus-4-5-20251101activeNot sooner than 2026-11-24Not published

Sources: Anthropic model deprecations , Claude Opus 4.5 , Model IDs and versioning , checked November 2, 2026.

Ids by platform

The Opus 4.5 model page lists these ids. The retirement line on that page is Not sooner than November 24, 2026. The deprecations page says which platforms that date covers. A partner platform can publish a different day.

The model IDs page says: "On the Claude API, these models also have shorter aliases (for example, claude-sonnet-4-5) that point to the most recent dated snapshot for that minor version." The deprecations table does not list claude-opus-4-5 by name. The Opus 4.5 page lists that alias next to claude-opus-4-5-20251101.

Microsoft Foundry and Claude Platform on AWS are in the Anthropic-operated list, and both ids on the model page are claude-opus-4-5. Claude Models on Google Cloud (Anthropic managed) uses claude-opus-4-5-20251101. Claude Models on Google Cloud (Google managed) uses claude-opus-4-5@20251101. Amazon Bedrock (InvokeModel) uses anthropic.claude-opus-4-5-20251101-v1:0. The deprecations page says those two partner platforms set their own schedules. This guide does not store a Bedrock date or a Google-managed date for this model.

Model ids on the Claude Opus 4.5 page, and whether the November 24, 2026 floor applies.
PlatformModel idNovember 24, 2026 floor
Claude APIclaude-opus-4-5-20251101Yes. Deprecations page. It is a floor, not a shutdown day.
Claude API aliasclaude-opus-4-5The alias points at the dated snapshot. The deprecations table does not list the alias by name.
Microsoft Foundryclaude-opus-4-5Yes. Anthropic-operated platform. Same floor, not a fixed day.
Claude Platform on AWSclaude-opus-4-5Yes. Anthropic-operated platform. This is not the Bedrock id.
Claude Models on Google Cloud (Anthropic managed)claude-opus-4-5-20251101Yes. Anthropic-operated platform. Same floor, not a fixed day.
Claude Models on Google Cloud (Google managed)claude-opus-4-5@20251101No. That platform sets its own schedule. No date is stored here.
Amazon Bedrock (InvokeModel)anthropic.claude-opus-4-5-20251101-v1:0No. Bedrock sets its own schedule. No Bedrock row is stored for this id.

Sources: Anthropic model deprecations , Claude Opus 4.5 , Model IDs and versioning , checked November 2, 2026.

Copilot uses another date

GitHub's Copilot retirement history lists Claude Opus 4.5 with retirement date 2026-09-01 and suggested alternative Latest Claude Opus model. That phrase is not a model id. The stored Copilot row is Claude Opus 4.5, shutdown date 2026-09-01, status retired. The August 31, 2026 changelog names Claude Opus 4.7, Claude Opus 4.8, or Claude Opus 5. Those names are Copilot models, not a Claude API replacement.

That Copilot date is already past on the day this guide was checked. It is not November 24, 2026. A Claude API string and a Copilot display name can sit in the same repository and still follow different pages.

Opus 4.5 dates that are not the same fact.
HostIdDate on that host's page
Claude APIclaude-opus-4-5-20251101Not sooner than 2026-11-24
GitHub CopilotClaude Opus 4.52026-09-01

Sources: Anthropic model deprecations , GitHub Copilot supported models , GitHub Changelog, August 31, 2026 , checked November 2, 2026.

No replacement on the deprecations page

The deprecation history does not list claude-opus-4-5-20251101. Deprecated models on that page get a recommended replacement. This id is Active, so the replacement column is Not published. This guide does not fill one in.

The Opus 4.5 page says: "Although Claude Opus 4.5 is still available, you should consider migrating to Claude Opus 5.5." It links Claude Opus 5.5 as the current Opus model and links the migration guide. claude-opus-5-5 is Active on the deprecations table, with tentative retirement not sooner than September 22, 2027. That is a documented model you can test. It is not the stored replacement.

The models overview is the current models list. The table below is every Active Opus id stored from the deprecations status table. Read that overview, and the model page for the id you might call, before you change a request.

Active Opus ids on the deprecations status table. None of these is a stored replacement for claude-opus-4-5-20251101.
Model idStatusDate on the deprecations tableRecommended replacement
claude-opus-4-5-20251101activeNot sooner than 2026-11-24Not published
claude-opus-5-5activeNot sooner than 2027-09-22Not published
claude-opus-5activeNot sooner than 2027-07-24Not published
claude-opus-4-8activeNot sooner than 2027-05-28Not published
claude-opus-4-7activeNot sooner than 2027-04-16Not published
claude-opus-4-6activeNot sooner than 2027-02-05Not published

Sources: Anthropic model deprecations , Claude Opus 4.5 , Claude Opus 5.5 , Models overview , checked November 2, 2026.

Find the id in code and config

Search the repository for the Claude API id, the alias, the Bedrock id, and the Google-managed id. A hit on claude-opus-4-5 can be the dated snapshot, the alias, Foundry, or Claude Platform on AWS, because the alias is a prefix of the dated id. Read the host in that file before you change it. A hit on the Bedrock id or the Copilot name is a different page.

The deprecations page tells you to open the Usage page in Claude Console, click Export, and then: "Review the downloaded CSV to see usage broken down by API key and model." That audit is written for deprecated models. This id is Active. The same CSV still breaks usage down by model, so it shows whether a key called claude-opus-4-5-20251101.

LangChain puts the id on ChatAnthropic as model=. LiteLLM puts a provider string in model, such as anthropic/claude-opus-4-5-20251101. Also search env files, YAML, TOML, and JSON. How to find every model ID in your codebase covers the other SDK argument names.

The scan page builds a search from dataset ids that have a shutdown date and a status other than active. claude-opus-4-5-20251101 is active, so it is not on that list. Search for it yourself. The GitHub Action does not fail a not_before date.

ripgrep

rg -n -e 'claude-opus-4-5-20251101' -e 'claude-opus-4-5' -e 'claude-opus-4-5@20251101' -e 'anthropic.claude-opus-4-5-20251101-v1:0' -e 'Claude Opus 4.5'

Sources: Claude Opus 4.5 , Anthropic model deprecations , Model IDs and versioning , checked November 2, 2026.

What callers see after retirement

Nothing on the deprecations page says claude-opus-4-5-20251101 stops on November 24, 2026. If Anthropic later retires it, the page defines Retired as: "The model is no longer available for use. Requests to retired models fail." It also says: "Requests to models past the retirement date will fail."

That page does not print an HTTP status or an error sentence for a retired model. This guide does not invent one. The errors page says HTTP 404 is not_found_error, and the example message is The requested resource could not be found.. Catch a retired model before your users do records that the deprecations page does not name not_found_error, and does not say every retired id uses that type.

A 400 from a field claude-opus-5-5 rejects is a different failure. It happens when the new id is already in the request and an old setting is still there. Those sentences are in the next section. temperature, top_p, and top_k return 400 on API version 2026-10-21 is the API version rule. It is not this retirement.

Sources: Anthropic model deprecations , Anthropic API errors , checked November 2, 2026.

If you call claude-opus-5-5

Use this section only if you choose claude-opus-5-5 because the Opus 4.5 page says to consider it. The deprecations history does not name it as the replacement. The stored row is claude-opus-5-5. The migration guide says to change the model id to claude-opus-5-5. claude-opus-5-5 has no date suffix.

The migration guide says: "Where an item says a setting is rejected, the API returns a 400 error." It says to omit temperature, top_p, and top_k. It prints a 400 for thinking type disabled and for a thinking budget: ""thinking.type.disabled" is not supported for this model." and ""thinking.type.enabled" is not supported for this model." Send no thinking field, or send thinking type adaptive. Set output_config.effort. The same guide says the default effort on claude-opus-5-5 is medium.

The migration guide says: "Prefilling assistant messages returns a 400 error on Claude Opus 4.6 and later Opus models, including Claude Opus 5.5, so this is a change only if you come from Claude Opus 4.5 or earlier." It also prints: "tool_choice: type "tool" and "any" are not supported for this model." Send tool_choice type auto or none. Read content blocks by type, because a response can start with a thinking block. Pass thinking blocks back unchanged in a tool loop.

The migration guide also says to move off client.beta.messages.create, to remove the effort-2025-11-24, fine-grained-tool-streaming-2025-05-14, and interleaved-thinking-2025-05-14 beta headers, and to move output_format to output_config.format. The full checklist is on that page. The snippet below is the Claude API call. It is not a Bedrock id and not a Copilot name.

Python Messages API shape from the Opus 5.5 migration guide. Not a stored replacement.

import anthropic
client = anthropic.Anthropic()
message = client.messages.create(
    model="claude-opus-5-5",
    max_tokens=16000,
    output_config={"effort": "medium"},
    messages=[{"role": "user", "content": "Hello"}],
)

Sources: Migrate to Claude Opus 5.5 , Claude Opus 5.5 , Claude Opus 4.5 , checked November 2, 2026.

Related SunsetDiff pages

All guides

Questions

Does claude-opus-4-5-20251101 shut down on November 24, 2026?

No. The deprecations table lists it as Active, Deprecated N/A, tentative retirement not sooner than 2026-11-24. That is the earliest possible shutdown. The page says: "The model is fully supported and recommended for use." It also says: "Anthropic notifies customers with active deployments for models with upcoming retirements, providing at least 60 days' notice before model retirement for publicly released models."

What is the recommended replacement?

Not published. The deprecation history does not name one. The recommended replacement is the official replacement stored on each row. claude-opus-4-5-20251101: Not published. The Opus 4.5 page says: "Although Claude Opus 4.5 is still available, you should consider migrating to Claude Opus 5.5." The current models list is the models overview. claude-opus-5-5 is on that list, and the deprecations table lists it as Active. It is not stored as the replacement.

What error does a retired call return?

The model is not retired. If it is retired later, the deprecations page says: "The model is no longer available for use. Requests to retired models fail." It also says: "Requests to models past the retirement date will fail." It does not print an HTTP status or an error sentence. The errors page says HTTP 404 is not_found_error, and the example message is The requested resource could not be found.. The deprecations page does not name not_found_error. This page does not invent a retirement error.

Does Amazon Bedrock or GitHub Copilot use November 24, 2026?

No date is stored for Bedrock id anthropic.claude-opus-4-5-20251101-v1:0. The deprecations page says Bedrock sets its own schedule. Copilot lists Claude Opus 4.5 with retirement date 2026-09-01 and suggested alternative Latest Claude Opus model.

Is there a /shutdowns/anthropic-2026-11-24/ page?

Yes. /shutdowns/anthropic-2026-11-24/ lists claude-opus-4-5-20251101. The date is kind not_before. It is the earliest possible shutdown, not the day the model stops.

More guides

Deprecation alerts

We email you before models shut down. Unsubscribe anytime.

Deprecation alert signup
Providers (optional)