Open any major AI product right now and you'll see the same primitive. A text input with a send button. ChatGPT. Claude. Perplexity. Gemini. The dozens of vertical AI products that have shipped in the last year, for coding, medical questions, legal, marketing, therapy. They all default to chat.
The convergence is striking, and I want to argue it's a design failure rather than a design pattern.
Chat became the default not because it's the right interface but because it was the easiest interface to ship for a research preview. ChatGPT was a tech demo that accidentally got famous. Chat was the format that exposed the model's general-purpose capability cheaply. Every product that followed copied the interface because chat looked like the AI interface. That was skeuomorphism, the same way early websites had paper-textured backgrounds and skeuomorphic file folders.
Apply Irvan's foundation lens of the four publics. Every product has four audiences: the user, the buyer, the regulator, and the surrounding ecosystem. Chat collapses all of them into one interaction surface, optimized for a single audience: the curious individual exploring capability. It's hostile to the other three. The buyer (a manager deploying the tool to a team) gets no admin layer, no policy surface, no analytics. The regulator gets a black box. The ecosystem gets no integration points beyond paste-and-pray.
A thought experiment. If you were designing a software tool for legal contract review and had no preconceptions, would you make it a chat box. Almost certainly not. You'd make a document-first interface with the AI as a side panel. Comments, suggestions, redlines. The chat surface would be a secondary affordance, used for asking "why did you flag this clause." Yet most legal AI tools ship as chat. The legal tool decided to be a chat box because that's what AI products are, not because that's what the work needs.
Apply foundation principle Constraint inversion. What constraint would make the answer obvious.
Constraint: the AI cannot show a chat box. The user must accomplish the same job through artifact-first interactions. What does the product become.
For coding, it becomes the IDE with deep agentic capability inside it. The agent operates on files and produces diffs. The conversation, when needed, is about specific diffs. Not a free-form chat. Cursor and Claude Code are early examples. They're winning because they understood this.
For research, it becomes a research workspace with documents, sources, annotations, and an agent operating on them. The user adds a source. The agent enriches it. The user marks a passage. The agent expands it.
For therapy, it becomes a journal. Structured prompts, mood tracking, reflection artifacts that build over weeks, an agent that responds in the margins. Not a chat. A relationship encoded as a growing document.
For legal, an annotated document. Redlines. A contract that improves over conversation, rather than a chat about a contract that lives elsewhere.
The shared move in all of these is the same. The artifact becomes the interface, and the AI is everywhere around the artifact, contextually summoned. Chat is a secondary modality. A fallback for genuinely conversational questions, not the primary surface.
Every team building an AI product right now is making the wrong default decision and shipping it. In five years we'll look back at this generation of AI chat apps the way we look at 2002 enterprise software. Bloated, undifferentiated, obvious in retrospect. The teams that figure out the artifact-first move now will own the second wave.
.webp)
.webp)
.webp)
