Autonomous Mode Display

Autonomous mode display is an AI UX pattern that keeps a persistent, glanceable signal when an agent is running unattended—badge, banner, or status light. Users always know automation is live and can interrupt it.

Share

Interactive demo

Idle

Asks before each step

Agent

Fix flaky auth tests

I’ll pause before each step unless you let me run on my own.


Opened auth.test.ts
Updated retry helper
Running test suite

Overview

The design problem

How might we design autonomous mode display so people can trust and act on AI output?

Use this pattern

When this pattern fits

  • Essential for AI coding agents, always-on assistants, and automated workflows where unattended execution needs a glanceable, always-visible signal so users never discover autonomy by surprise.

Avoid this pattern

When to skip or lighten it

  • Fully manual copilots that never run without a keystroke.
  • Backend jobs with no user-facing surface (use ops dashboards instead).
  • Momentary generations shorter than a status animation would help.

States

State model coming soon

Key UX elements

Key UX elements coming soon

Anti-patterns to avoid

  • Autonomous runs with no visible indicator.

  • Indicators that stay on after the agent stopped.

  • No path from the indicator to pause, stop, or logs.

  • Decorating marketing screenshots with fake “live” badges.

How products use it

ProductImplementation
CursorAgent badges and status while background runs continue.
Tesla AutopilotPersistent driving-assistance state in the cabin UI.
macOSMenu bar microphone and screen-sharing indicators.
iOSOrange/green status dots for mic and camera use.

Implementation

Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.

Generate a production-ready implementation of the "Autonomous Mode Display" AI interface design pattern.

Pattern Definition:

Frequently asked questions

What is autonomous mode display?

It is a persistent UI signal that an agent is acting without continuous user input, so people can notice and intervene.

Where should the signal live?

In a global chrome location: top bar, menu bar, or session header. Do not bury it inside a scrolled transcript.

What actions should it offer?

Pause, stop, open live log, and view permissions. Status without control is incomplete.

How does it differ from ambient presence displays?

Autonomous mode is specifically “unattended run is active.” Ambient presence covers broader low-attention agent states, including idle listening.

Weekly AI UX in your inbox

Weekly AI interface UX notes and resources on Substack, no spam, unsubscribe anytime.

Subscribe on Substack