Spend enough time with new web apps and they start to blur: the same rounded cards, the same muted greys, the same faint outline on every button. That sameness has a source. A lot of those screens were generated by AI tools reaching, by default, for the same parts — shadcn/ui, which began in 2023 as one developer’s copy-paste collection of React components, the kind of side project you star and forget. Three years on, it’s what Vercel’s v0, Cursor, Claude Code, GitHub Copilot and OpenAI’s Codex pull from when you ask them to build a screen. And on July 2, 2026, its maintainers quietly swapped the machinery under every component from Radix UI to Base UI — a one-line changelog entry with a long reach, because shadcn/ui is no longer a library developers pick. It’s a default that AI agents pick for them, thousands of times a day, with no design team in the room.
How one library became AI coding’s shared default
The how isn’t mysterious once you watch these tools build a screen. According to the Vibe Coder Blog, shadcn/ui’s clean, Tailwind-based code is exactly the material the models trained on, so v0 “outputs shadcn UI components by default.” shadcn/ui’s own registry documentation closes the loop: it ships a connector — a Model Context Protocol (MCP) server — that “works out of the box” with Claude Code, Cursor, Copilot, Codex and OpenCode, so an agent can search, fetch, and install components itself. And once it spots shadcn/ui in a project, it reaches for shadcn/ui on everything after — which is how, as writer Luis Ouriach put it in “The shadcn-ification of the internet”, so many AI-built apps land on the same card radius, the same greys, the same ghost buttons.
A design system used to be a deliberate artifact, argued out in critique and documented for a reason; shadcn/ui spread instead as the path of least resistance for a model, with none of that deliberation. The decisions haven’t stopped — they’ve just left the room where people used to argue about them.
What an upstream default costs the teams downstream
The Base UI switch is the clearest look at that dependency, because the cost lands on people who never made the call. shadcn/ui’s changelog is blunt: “Starting today, Base UI is the default component library in shadcn/ui.” The reason given is momentum — Base UI had passed “over 6 million weekly downloads,” and new projects were already picking it over Radix two to one. But that does nothing for a team with an existing codebase, and a GitHub discussion on the transition spells out the chores: an attribute quietly disappears, a checkbox setting turns stricter, and the whole form layer has to be rebuilt. shadcn/ui’s fix is to hand the migration to an AI agent rather than a script, “because you own the code” — a line that sounds like freedom and also means the maintainer sets direction while your team does the moving.
The look of thousands of apps is now set less by any design team than by one maintainer's defaults and a model's training data.
Why “nobody chose it” doesn’t quite survive the download numbers
The honest complication is shadcn/ui’s own restraint. The same changelog says “you do not need to migrate,” that Radix “is not being deprecated,” and that every component still ships for both libraries. That reads less like a monoculture and more like a maintainer writing down a preference thousands of developers had already made, one project at a time, around a library with real accessibility gains. Developers are not silent here; their say is just cast one command at a time, pooled invisibly into a dashboard, then re-issued as a default the next agent applies to a thousand more projects without anyone revisiting it. Which is how the look of thousands of apps is now set less by any design team than by one maintainer’s defaults and a model’s training data. The same pattern surfaced one layer down with Open VSX, the registry nearly every AI editor quietly runs on; here it shows up in the pixels people actually touch. Individual choice adds up to structural consequence faster now, and with far less visibility, than when adopting a design system meant a team sat down and argued.
