Digital Transformation · 18 October 2026
Replit switches default AI model to OpenAI from Anthropic
Replit will make OpenAI its default model provider in place of Anthropic, according to CEO Masad. Anthropic's Claude models remain available to customers on the platform.
What happened
Replit will make OpenAI its default model provider in place of Anthropic, according to the company's chief executive, Masad. Anthropic's Claude models will remain available to customers on the platform.
Masad clarified the change over the weekend. TechCrunch reported the development on 17 October 2026 under the headline that Replit is no longer working with Anthropic. The framing differs from the CEO's own description, which presents the change as a shift in default provider rather than a removal of Anthropic from the product.
Why it matters
For an AI-powered development platform, the default model is the one most users meet first. Changing it is a product decision with direct experience consequences, because it shapes the speed, tone and output quality people encounter before they choose anything themselves. The reporting does not set out the reasons for the switch or any comparative performance data, so the change should be read as a platform-level decision rather than evidence about either model's relative quality.
The development also shows how quickly model supply can shift inside AI-native products. Organisations that build on third-party models are reminded that vendor relationships can change at the platform layer while customer-facing access to alternatives persists.
The Renascence take
Most coverage will treat this as a vendor rivalry story. The more useful lens is the default itself.
A default is a behavioural nudge, and most users never change it, so the choice of model is effectively the experience for the majority. Operators running AI-enabled products should audit which model they route to by default, what users notice when it changes, and whether the experience holds for people who never think about the model at all. Treat model providers as swappable service components in your design, and write that dependency into your service blueprint now rather than after the next switch.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in Digital Transformation
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


