DEV Community

Cover image for Agentic UX Is Changing What We Mean by an Interface
Kalpick Sharma
Kalpick Sharma

Posted on

Agentic UX Is Changing What We Mean by an Interface

For years, frontend developers and designers have worked with a simple mental model:

User → UI → Application

The user clicks something.

The application responds.

But agentic AI introduces another possibility:

User → Intent → AI Agent → Tools → Application

Now the software can perform actions on behalf of the user.

That sounds like an AI engineering problem.

I think it's also a UX problem.

The user may not perform the action anymore

Imagine a user says:

"Find unused subscriptions and reduce our monthly costs."

A traditional application makes the user do the work.

An agent could potentially:

Understand intent

Review data

Find candidates

Plan actions

Ask for approval

Execute changes

The user's job becomes less about clicking and more about delegating.

That changes what the interface needs to communicate.

We need more than buttons

Traditional UI components are designed around human actions:

Button
Form
Modal
Dropdown
Table
Toast

Agentic systems introduce different concepts:

Intent
Permission
Agent state
Approval
Action history
Intervention
Recovery

These aren't necessarily components you can simply drop into a React application.

They are interaction patterns.

Agent state becomes important

A traditional loading state might be enough for a network request.

An agent can have a much richer lifecycle:

Planning

Executing

Waiting for approval

Completed

Needs intervention

For example:

const statusText = {
planning: "Planning the next steps",
executing: "Working on the task",
approval: "Waiting for your approval",
completed: "Task completed",
intervention: "Your input is required",
};

function AgentStatus({ status }) {
return {statusText[status]};
}

The code is simple.

The design decision isn't.

The user needs to understand what the agent is currently doing.

Don't make users approve everything

If an agent asks for confirmation before every action, the user becomes the bottleneck.

A better model is to think about risk.

Low risk
→ automatic

Medium risk
→ explain + intervention

High risk
→ human approval

Anthropic has described this kind of balance between agent autonomy and human approval for higher-impact actions.

The goal isn't maximum autonomy.

It's appropriate autonomy.

What happened after I said "go"?

This might become one of the most important UX questions.

An agent shouldn't always finish with:

"Done."

The user may need:

What happened?
What changed?
Why?
What data was used?
What is still pending?
Can I undo it?

Microsoft's Agent UX guidance emphasizes transparency and control, including making background agent activity visible and controllable.

That makes action history a useful design primitive.

Maybe the agent doesn't need the UI

GUI agents are already being researched as systems capable of interacting with graphical interfaces autonomously.

But agents can also interact through tools and APIs.

So the future product architecture could look like:

          Product
         /       \
     Human       Agent
       ↓           ↓
      UI       API / Tools
Enter fullscreen mode Exit fullscreen mode

The human gets visual interaction.

The agent gets structured capabilities.

This means frontend developers may eventually need to think about how their application's capabilities can be safely exposed to agents, not just how they look on screen.

The interesting UX shift

Traditional UX asks:

"How do I help the user complete this task?"

Agentic UX may increasingly ask:

"How do I help the user safely delegate this task?"

That's a very different question.

The interface becomes less about controlling every action and more about:

delegation + visibility + permission + recovery

And that is probably where Agentic UX gets interesting.

Key takeaways
Agents change users from operators into delegators.
Agent state should be treated as part of the UX.
Permissions and approval need deliberate design.
Action history becomes important when agents can perform multiple steps.
APIs and tools may become as important to agents as visual UI is to humans.
Good agentic UX balances autonomy with human control.

UI ab sirf humans ke liye nahi, AI agents ke liye bhi optimize karna padega jo screen ke bina kaam karte hain.

UX is shifting from actions to intent.

Top comments (0)