Vercel published a case for treating agents as a distinct class of software user. An agent calling your service behaves in a different way from a human clicking through it, so a separate testing track is needed to know whether your service works for agents. That reframe has direct consequences for how teams build and validate software that agents will use. The practical shift is in what you test and when. A human can recover from an ambiguous response or a broken flow. An agent often cannot. It may misread a response, take a wrong branch, and compound the error across many subsequent steps. Vercel's position is that you need test cases written around agent behavior, run against a defined configuration, and compared over time. That lets you see quality drift before it reaches production. For product and design teams, the people building agent-facing surfaces need to write down what good looks like, in the form of concrete examples a test can check. That work, turning a designer's or product manager's judgment into a repeatable standard, is the new craft this model demands. Without it, a team has no reliable signal that a prompt change helped or hurt the agents depending on it.