The design patterns of the AI-native interface
Agents are conversational, uncertain, tool-using and metered. That created a new set of UX problems, and a new set of patterns to solve them. Here is the reference, with each pattern graded by how well it is evidenced, and live demos.
Explore the patternspatterns on a peer-reviewed or research-backed spine
patterns widely practiced but barely documented, the white space
real products oversold as a settled paradigm
Why a new discipline appeared
For thirty years we designed for deterministic software. You clicked a button, the same thing happened every time, and the interface’s job was to make the available actions obvious.
Agents broke that contract. They are conversational, so the chat input became the primary surface. They are uncertain, so you have to communicate how sure they are. They take actions in the real world, so you have to show what they are doing and ask before they do it. They cost money per turn, so usage became something users watch with anxiety. None of these were interface problems two years ago.
Not all of these patterns are equal. Some sit on a peer-reviewed foundation. Some are widely practiced but barely documented. A few are vendor hype dressed up as a paradigm. This report separates them honestly, because building on the wrong one is how you lose a user’s trust.
The pattern taxonomy
Ten patterns, honestly graded. Select one to see what it is and how well evidenced it is.
Calibrated confidence
Verified spineSurface how sure the agent is, in a way that prevents overreliance rather than manufacturing it.
Every agent answer carries uncertainty. The naive fix is to show the reasoning trace and let the user judge. The research says that backfires: a fluent explanation reads as a competence signal and makes people trust a wrong answer more, not less.
The pattern that works is calibrated confidence: a small, honest signal of certainty, the specific part the agent is unsure about, and a one-tap way to verify. Confidence theatre is the anti-pattern.
The deep dives
Each pattern gets its own piece, with a live demo you can feel. More are landing in this series.
Calibrated confidence
Surface how sure the agent is, in a way that prevents overreliance rather than manufacturing it.
Read the patternVerified spineTool-call transparency and write-confirm
Show what the agent is doing, and confirm before it changes anything in the real world.
Read the patternObserved conventionInline citations and source grounding
Attach the source to the claim, in the answer, as a pill or footnote the user can open.
Read the patternObserved conventionToken and cost-transparency UX
Show the balance and what each turn costs, because metered AI creates real anxiety.
Read the patternObserved conventionThe video-call frame for voice agents
Borrow the video-call layout so talking to an AI feels familiar: agent as the main character, you as the small self-view.
Read the patternObserved conventionNaming the agent
A named agent with a defined voice is a product. A generic AI assistant is a feature nobody remembers.
Read the patternContested frontierArtifacts versus the chat stream
Some outputs cannot live in a scrolling transcript. They need their own surface.
Read the patternHow we got here: 2022 to 2026
Each pattern is a response to something that changed in the technology.
- ChatGPT launches (Nov 2022). The conversation, not the form, becomes the primary interface. The persistent input fixed at the bottom of the screen arrives as the default.
- Streaming responses, stop generating, regenerate and thumbs up/down feedback become standard.
- Bing Chat and Perplexity push inline citations into the mainstream. Grounding becomes an expectation.
- The first plugins and tool calls appear. Users start needing to see what the model is doing on their behalf.
- Claude Artifacts (Jun 2024) and ChatGPT Canvas (Oct 2024) move documents, code and apps out of the transcript into dedicated surfaces.
- The Model Context Protocol (Anthropic, late 2024) standardises tool calling, which forces a consistent connect, authorise and act flow.
- Agentic modes, computer use and plan-style review normalise the read-freely / write-confirm pattern.
- Voice and video agents adopt the familiar call layout. Realistic and abstract avatars compete.
- Microsoft Design publishes explicit UX guidance for agents: actions must be visible and controllable.
- Token and cost transparency become a felt UX requirement as metered usage spreads.
- The transparency backfire debate lands: ACM research shows naive reasoning displays can increase overreliance, raising the bar to calibrated confidence.
- The EU AI Act transparency obligations (Aug 2026) turn several of these patterns from good practice into expectation.
The foundations
The field has a real, citable backbone. These are the sources the durable patterns rest on.
Frequently asked questions
Don’t just read this. Put it to work.
The whole series is distilled into one Markdown file: every pattern, the do and don’t rules, and how well each is evidenced. Download it into your project, or paste the link into any chat with your agent and tell it to improve your agent UX. It’s free, no sign-up, no attribution required.
Use these Agent UX principles to review and improve our agent's interface: https://p0stman.com/agent-ux/agent-ux-principles.md
Start with the pattern that matters most
The clearest, most under-served pattern in the whole field is also the one most likely to break trust if you get it wrong. We wrote the definitive piece on it, with a live demo of confidence theatre versus calibrated confidence, so you can feel the difference.