Half of designers have shipped AI-generated code to production. Only 20% identify as design engineers. That gap tells you where the profession thinks the edge is.
The question used to be simple. What does the user see? What do they tap? Where does the error state go? Screens and flows. The deliverable was a picture of the product, and the picture was enough because the product was pictures. Interfaces rendered, users clicked, designers designed the click.
Agents don't click. They read, decide, route, act, escalate. Sometimes they do this while nobody is watching. Microsoft's design guidance for agents states that "agents that operate as background processes have a user-facing mechanism to view and control actions and automations." The mechanism matters. But the design problem most teams skip is what the agent does before a human ever opens it.
The agent extension test breaks most design practices here. The test asks one thing: can your design judgment survive when there is no screen to apply it to? When the product is a behavior?
For most designers working today, the answer is no.
Srinu Ippili, writing in UXmatters, put it clearly: "We are no longer designing static screens for users to navigate; we are designing behaviors, trust protocols, and hand-off points for human supervisors." That sentence names three things designers must now deliver. Only one of them (hand-off points) maps to anything a Figma file can express.
The other two require a different artifact. A behavioral specification. A document that defines: the agent will do X when it encounters Y. It will escalate to a human when Z. It will refuse when W. It will explain its reasoning in this format. It will lose access to these capabilities after this event.
Esteban Fernandez defines an agent persona as "a product specification for what the agent reads, decides, routes, acts on, escalates, proves, and can no longer do when access is revoked." His framework produces an operating contract from that persona, one that engineering, security, operations, compliance, support, and product can all challenge.
A study of behavioral contracts for AI agents across 1,980 sessions on seven models found that contracted agents detected 5.2 to 6.8 soft violations per session that went undetected by baselines. The violations existed either way. The specification made them visible.
Expectations haven't caught up. 43% of companies now expect working prototypes as deliverables. 65% of designers said they're taking on more product or engineering responsibilities. Companies are asking designers to do more. But "more" still means more of the same kind of work. More prototypes and more screens, faster. Not a different kind of work entirely.
Jakob Nielsen put it bluntly: "UI design, as traditionally conceived, becomes irrelevant." That overstates it. Agents still need interfaces for transparency and control. Microsoft is right that those remain foundational. But the balance has shifted. The interface is the audit layer.
So who writes the behavioral specification? Right now, in most teams, nobody. The gap shows up in the research: AI agents operate on prompts and natural language instructions with no formal behavioral specification. Engineers write prompts and product managers write user stories. Designers make screens for the settings page. The actual behavior, what the agent does when it is alone with the user's data, gets designed by default. By whoever wrote the system prompt last.
80% of designers say they rely on their own judgment for quality, craft, and creative direction. Good. Judgment compounds. But if you only apply it to pixels, it has a ceiling. The designer who can specify agent behavior, who can write the contract for what an agent does and refuses to do, brings that same judgment to a higher altitude.
The deliverable changed. The skill did not. You sequence decisions, define boundaries, anticipate failure modes, make tradeoffs legible to a team. That has always been design work. Whether you need a canvas to do it is a separate question.