Why you shouldn't leave model selection on default in Copilot, Gemini and other AI tools
Source published ·Modelwire updated
Original coverage: The Decoder ↗·How Modelwire adds context
The development
Default model selection in mainstream AI assistants masks a critical reliability gap: identical inputs produce wildly different outputs depending on which underlying model processes them. Mathematician Adam Kucharski's experiment with Copilot revealed the tool fabricates country-specific stereotypes when fed unlabeled data, a failure that advanced reasoning models catch but only when users explicitly select them. This exposes a usability and trust problem at scale. As AI tools embed deeper into workflows, burying model choice behind defaults risks systematizing hallucination and bias without user awareness or recourse.
Modelwire’s AI-generated summary of coverage from The Decoder.
Modelwire analysis
ExplainerOur AI-generated reading of the wider context and the next developments to watch.
The deeper issue isn't that weaker models hallucinate, which is well-documented, but that product interfaces actively obscure which model is running, removing the user's ability to make an informed choice before the output is already trusted and acted upon.
This story is largely disconnected from recent Modelwire coverage, including the WIRED piece on robotic meal prep in San Francisco's Tenderloin, which sits in a different domain entirely (physical automation in nonprofit services). The default-model problem belongs to a cluster of AI reliability and deployment-trust questions that have surfaced repeatedly around enterprise tooling. The core tension here is that the same interface abstraction that makes AI tools accessible to non-technical users also strips away the controls that technically informed users rely on to get consistent results. That gap widens as organizations embed these tools into consequential workflows without auditing which model tier is actually processing their inputs.
Watch whether Microsoft or Google update their Copilot and Gemini default configurations to surface active model selection more prominently in the next two product release cycles. If neither does, that signals the interface obscurity is a deliberate retention-of-simplicity choice rather than an oversight.
This interpretation is generated from the summary above and available source metadata. Our methodology · Report an error
MentionsMicrosoft Copilot · Google Gemini · Adam Kucharski
How this coverage is produced
Modelwire uses AI to generate summaries and context from source headlines, snippets, and selected archive coverage. Automated checks do not verify every claim, and items are not routinely reviewed by a person before publication. Zacaria Solis operates the site. Read the linked source for the full evidence and report errors through our corrections process.
Modelwire summarizes, we don’t republish. The full content lives on the-decoder.com. If you’re a publisher and want a different summarization policy for your work, see our takedown page.