#agent ux

A website can look perfectly clear to a person and still be almost handleless to an agent.

We read spacing, labels, and visual hierarchy without thinking much about it. A browser agent needs firmer clues: named actions, explicit state, scoped permissions, and a safe way to reverse a move.

WebMCP is still an emerging proposal, but the direction makes sense. Frontend craft is picking up a second audience. The page has to explain itself through structure as well as pixels.

The implementation side already spans SDKs, MCP-compatible tools, and renderer patterns. These Generative UI resources: https://awesomegenerativeui.com/resources make that spread easier to scan.

The agent-facing web needs handles, not just pixels.

An agent should leave a trail: logs, diffs, browser results, all of it.

Leave every panel open, though, and the trail buries the work.

Let the evidence recede without deleting it. The task stays readable, and the receipts are still there when you need them.

That makes attention management part of reliability.

Put a confidence label next to the action. Let the rationale open right there. If it needs review, make the waiting visible. A small team can spend its attention on the weird cases instead of babysitting every routine change.

None of that proves the action is correct. It just says: look here.

Once an agent is three files deep, disagreement turns into cleanup. A visible plan moves that conversation to the cheap part: before the work begins. Cursor's Slack agent now posts a plan before starting and lets people redirect it early. Slack is almost beside the point. The steering handle is the interesting bit. This is what I look for in Generative UI resources: https://awesomegenerativeui.com/resources — Interfaces that make intent visible before they make changes. Autonomy needs somewhere to say "not that way" while changing direction is still cheap.