The Wrapper Eats Itself

It went like this.

First, people discovered the raw capability and built the simplest possible interface on top of it — chat with your PDF, summarize this doc, ask your contract a question. The "GPT wrapper" era, named dismissively by people who were also building GPT wrappers. A thousand startups, all of them pointing at the same underlying thing, all of them hoping nobody noticed.

Then the labs noticed. Retrieval, document parsing, long context — API functions now. The wrapper became a checkbox in a pricing tier. This was described as inevitable and it was, which didn't make it less brutal for whoever had just raised a seed round on that exact feature.

But that was the polite version of the squeeze. The impolite version is what's happening now.

The labs are shipping full product suites — coworking tools, research assistants, interfaces with enough surface area that the product becomes the thing people talk about. Not "I'm using a model that can maintain context across a 200-tool environment with persistent memory and structured outputs." Just: "I use Claude for work." The capability disappears into the brand.

In the wrapper era, a weird accidental thing happened — a hundred thousand developers got fluent in exactly what these models could and couldn't do. They were poking at the seams, hitting the context limits, working around the hallucinations, building scaffolding. The machinery was visible because it had to be. You couldn't hide a 4096-token window from the person designing around it.

That era is over. The new user sees a product release, maybe reads the announcement, and the multitudes underneath — the retrieval pipeline, the tool use, the multi-agent orchestration, whatever they stapled together this quarter — are just vibes. It works or it doesn't. The model is the interface now.

The labs didn't just take back the market. They took back the legibility.

Which is a reasonable business decision and a strange epistemological one — the most powerful software infrastructure in a generation, increasingly understood in detail by fewer people, while being used by more. The wrapper ate itself and became something most of its users will never have reason to unwrap.

That's not a problem yet. It's just a fact that will become a problem later, dressed up right now as a product launch.