Skip to content
AAA.win
EN
EnglishEN中文ZH日本語JAEspañolES
SearchSubmit a tool
Menu

change record

Anthropic's Claude 4 announcement: what evaluation teams should record

A source-linked record of Anthropic's May 2025 Claude 4 announcement and the test conditions it can affect.

Event date:

Editorially reviewedVerified 2026-08-112 official or primary sources

Product announcements are inputs to a retest plan, not independent proof that a model fits a specific workflow.

Anthropic announced Claude Opus 4 and Claude Sonnet 4 on May 22, 2025. The announcement discussed coding, reasoning, agent workflows, tool use, and Claude Code availability.

Those descriptions are provider claims tied to a dated launch. AAA.win preserves the event as a change signal while requiring separate, task-level evidence before recommending a deployment.

Teams comparing runs across this boundary should capture the exact model, whether extended thinking or tools were enabled, the product surface, and the repository or document context supplied to the model.

What changed

  • Anthropic introduced Claude Opus 4 and Claude Sonnet 4.
  • The announcement described both model and developer-tool changes.
  • Existing Claude evaluations could no longer be assumed to describe the newly announced configurations.

What to do now

  • Read the current model and product documentation before deployment.
  • Separate model quality from the effect of tools, context, and product integrations.
  • Rerun safety-critical and high-volume tasks before switching a workflow.

Sources checked

Open the original pages before relying on a time-sensitive product decision.

  1. Introducing Claude 4Anthropic
  2. Claude documentationAnthropic
Version · v4.3.4-indexnow-root-proof

Latest releases

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

IndexNow key-proof compatibility

Changed IndexNow verification to the official root-level {key}.txt convention after the first production notification returned HTTP 403; revalidation remains pending, while the website, sitemaps, and Bing sitemap processing are unaffected.

Bing sitemap discovery and IndexNow change notifications

Prepared canonical sitemap discovery for Bing and added automatic IndexNow change notifications while keeping segmented sitemaps authoritative and making no claim that a notified URL has been crawled or indexed.

View all releases