The underlying account was first reported by Reuters and then carried by UkrMedia News and Mezha. Reuters, citing three people familiar with the matter, says Anthropic is weighing a launch partly in response to OpenAI’s momentum and is evaluating the safety of its next model. Anthropic declined to comment. That distinction gets lost in headlines presenting a new “answer” to Astra as imminent: the report establishes that Anthropic is considering a release, not that it has approved one.
OpenAI, meanwhile, launched GPT-6 Astra on September 3, 2026, and says the model is rolling out to ChatGPT business customers, the OpenAI API, Microsoft Azure, and AWS Bedrock. For organizations already building on Azure AI services, that creates an actual deployment and governance decision today; a prospective Anthropic launch does not.
Reuters’ report is one story, not two confirmations
UkrMedia News and Mezha are separate publications, but both submitted items trace back to the same Reuters reporting. That means the central claim—Anthropic is weighing a new model—rests on Reuters’ unnamed sources, rather than on two independently confirmed reports or an Anthropic announcement.
Reuters reports that Anthropic is balancing a possible release against safety review and profitability concerns ahead of an expected initial public offering. It also reports that some prospective investors have reassessed Anthropic’s enterprise position after Astra’s debut. Those are credible reporting claims, but they should not be converted into a product roadmap.
As of September 19, Anthropic’s public newsroom lists its most recent model announcement as Claude Fable 5.1 and Claude Mythos 5.1, released September 1. The company has published recent material on misuse prevention, enterprise safeguards, and measurements for frontier-model development, but it has not named a successor model or issued a release notice matching the Reuters report.
That absence is more than a semantic point for administrators. A new frontier model can change context limits, tool behavior, rate limits, pricing, retention options, safety refusals, and output consistency. Until Anthropic publishes model documentation and commercial terms, enterprises cannot assess the work involved in adopting—or even evaluating—the rumored system.
GPT-6 Astra is already a Microsoft Azure planning issue
OpenAI says GPT-6 Astra is available as gpt-6-astra through its API and Microsoft Azure. Its stated standard API pricing is $10 per million input tokens and $50 per million output tokens, with higher rates for its faster processing mode. OpenAI also says Astra access is disabled by default for ChatGPT Enterprise workspaces at launch, requiring an administrator to enable it.
For Windows-centric organizations, the relevant question is not whether a future Claude model may top a benchmark. It is whether Astra’s current agentic capabilities belong in existing development, support, security, and automation workflows—and, if so, what guardrails have to change before it touches production systems.
OpenAI positions Astra as stronger at computer use, browser operation, software engineering, cybersecurity, and multistep professional tasks. Those are precisely the areas where a model is more likely to interact with source repositories, browser sessions, endpoint-management portals, cloud consoles, tickets, documents, and internal line-of-business software rather than simply draft text.
The company also says Astra has reached its highest internal preparedness level for cybersecurity capability. Its launch material says the model can identify unknown security flaws and develop exploits under some testing conditions, while production safeguards are intended to refuse more advanced offensive tasks. OpenAI acknowledges that the resulting monitoring may slow, pause, or stop legitimate defensive work; in the API, it says a stopped task ends rather than continuing automatically.
That creates a practical operational constraint: teams evaluating Astra for defensive security automation should expect workflow interruptions and build recovery paths around them. A test that succeeds in a supervised chat session is not proof that the same job will complete reliably when embedded in an unattended PowerShell, DevOps, help-desk, or browser-automation pipeline.
Enterprise spending figures are signals, not a verdict
Reuters cites Ramp data showing GPT-6 Astra at about 13% of enterprise AI spending tracked by the corporate-expense platform, compared with roughly 8% for Anthropic’s Claude Fable. It also reports that OpenRouter users spent more on OpenAI models than Anthropic models in the prior week—the first OpenAI lead on that particular measure in more than two and a half years.
Those are noteworthy indicators of short-term developer and business interest, but neither metric proves that OpenAI has displaced Anthropic inside large enterprise deployments. Ramp tracks a specific category of corporate spending, not all model consumption; OpenRouter reflects use through a third-party routing platform, not the many workloads that run directly through vendors, hyperscalers, or private infrastructure.
Reuters also reports that Anthropic’s annualized revenue run rate exceeded $65 billion by the end of July, compared with OpenAI’s reported $40 billion run rate in the same month. Even if those figures accurately reflect the companies’ internal measures, they are not comparable enough on their own to establish a durable winner. AI vendors can gain attention, API spending, or benchmark leadership while customers remain reluctant to replace deeply embedded models and tooling.
For enterprise buyers, the useful conclusion is that frontier-model leadership is becoming less stable, not that a wholesale migration is warranted. Organizations that designed their applications around a single provider’s prompts, tool schemas, and model-specific behavior will face the highest switching cost when the next release changes the competitive picture.
The safety tension is real, but it is not proof of hypocrisy
Reuters places Anthropic’s reported deliberations days after chief executive Dario Amodei argued publicly that advanced AI development should slow as capabilities outpace safeguards. Anthropic’s recent public materials likewise emphasize monitoring, misuse prevention, and its proposed measurements for the speed of frontier development.
A company can consistently advocate stricter release gates while still developing and evaluating a new model. The test is whether it publishes enough evidence to show that its gates have meaning when commercial pressure rises. So far, there is no announced Anthropic model on which to judge that question.
OpenAI faces an equivalent scrutiny problem with Astra. The company’s launch claims are extensive: it says Astra improves capability across coding, computer use, science, professional work, and cybersecurity. But many of the most dramatic comparisons in the launch material are OpenAI’s own measurements or partner statements, not broad independent production evidence.
That is why Windows developers and security teams should resist treating either vendor’s scorecards as procurement results. A model that performs well on a coding benchmark can still violate an organization’s logging requirements, fail at proprietary UI flows, mishandle authentication, produce difficult-to-review infrastructure changes, or trigger safety controls during a time-sensitive incident.
What teams should do before the next model cycle
Organizations evaluating GPT-6 Astra now should preserve a reproducible baseline before enabling it broadly. Keep a set of representative coding tasks, security-review cases, browser automation flows, document-processing jobs, and help-desk scenarios. Measure task completion, elapsed time, review burden, token cost, interruption rates, and failure recovery—not just answer quality.
They should also keep model calls behind an abstraction layer wherever possible. Separate prompts, tool definitions, evaluation harnesses, model identifiers, and safety policies from business logic. That will not make a provider switch painless, but it prevents a future Anthropic release—or an Astra revision—from turning into an unplanned application rewrite.
The Reuters report is a warning that the next competitive turn may arrive quickly. It is not, yet, a reason to delay an Azure-based Astra evaluation or to plan a migration to an unnamed Anthropic model. The next actionable event will be Anthropic publishing a product name, supported interfaces, pricing, access terms, and safety documentation that enterprise customers can actually test.