Anti-patterns

Confirm everything: why agents wrap routine actions in "Are you sure?"

The confirmation dialog is the agent's safety net. Applied to every action, not just destructive ones, it creates an interrupt-heavy experience that slows down every workflow it was meant to protect.

The most defensive button an agent will add to any interface is "Are you sure?" Confirm dialogs appear on archive actions, delete actions, publish actions, submit actions, and occasionally on close actions that navigate away from a form. Sometimes they appear with a second confirmation for good measure. The agent is being careful.

The problem is that care applied uniformly produces the same interface as carelessness — one where the user has tuned out the confirmation text entirely and clicks confirm on reflex. When that happens, the dialog isn't providing safety. It's providing the appearance of safety while adding a click to every action in the product.

When confirmation is the right answer

Confirmation dialogs have a legitimate use. The criteria are specific: the action is destructive AND irreversible, and the consequence of the mistake is significant.

Permanently deleting a record with no recovery path. Cancelling a subscription with immediate effect. Revoking access to a system with no reinstatement flow. These warrant a confirm step — ideally one that requires the user to demonstrate intent rather than just click a button. Typing the item's name, or the word "delete," forces a brief moment of active decision. It slows down the accidental and doesn't slow down the intentional.

Note what's absent from that list: archiving a draft, submitting a form, approving a recommendation, sending a message that can be recalled, and anything that routes to a review queue before taking final effect. These don't qualify. They're routine actions in a workflow, not one-way doors.

Pattern: confirmation dialogs are for actions that are both destructive and irreversible. For everything else, build undo instead — it provides real safety without interrupting the workflow.

Undo is the right answer for reversible actions

For actions that can be undone, the correct safety mechanism is an undo affordance — typically a dismissible toast that appears immediately after the action completes and offers a brief window to reverse it. Gmail's send undo. Notion's delete undo. The pattern is well-established because it's genuinely better: the action completes immediately (fast, no friction), the user has a real recovery path if they made a mistake, and the workflow is only interrupted if there was actually a mistake.

This is a better safety net than a confirm dialog for reversible actions. Confirm dialogs interrupt before the action, requiring a decision about whether to proceed. Undo affordances interrupt only if the action was wrong, requiring a decision to reverse. For routine actions in high-volume workflows, the confirm approach is strictly worse.

Why agents over-confirm

Agents default to confirmation dialogs for the same reason they default to modals: safety feels like a feature, and adding a confirm step is easy to scaffold. The agent sees a delete button and knows that deleting things can be bad. The confirm dialog is the obvious protective response.

What the agent doesn't model is the frequency at which the action occurs. Confirming a one-time account deletion is different from confirming every record archive in a batch workflow. The former is reasonable; the latter compiles into a significant time cost across a workday. An operator archiving fifty completed records confirms fifty times. None of those confirmations were necessary. All of them were interruptions.

How TheDesignAgent flags it

The /ux lens flags confirmation dialogs on actions that don't meet the destructive-and-irreversible bar. The extraneous_load sub-score reflects the interrupt cost, and the patch is direct: replace the confirm dialog with an undo toast on this action, reserve confirm step for the delete-permanently flow.

The distinction between "archive" and "delete permanently" is where agents most commonly conflate the two. Archive is reversible and should get undo. Delete permanently is not and should get a confirm. When both get a confirm dialog, the serious one reads the same as the routine one — and users learn to dismiss both without reading them.