AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Inputs

AI Context Menu

Offer AI actions on a selection such as summarize, rewrite, or explain via right-click or a floating toolbar. Help appears at the point of need without opening a separate chat first.

Interactive demo

Artificial Intelligence is changing...

Overview

How might we design ai context menu so people can trust and act on AI output?

When to use

  • Ideal for reading applications, browsers, and content platforms where contextual AI actions enhance user interaction without disrupting the reading experience.

When to skip

  • Read-only previews where actions cannot apply.
  • Selections that are too small to be meaningful.
  • Apps that already dedicate primary chrome to the same actions.

Rules

  • Menus with twenty vague AI verbs.

  • Actions that rewrite far beyond the selection without preview.

  • No keyboard access to the same actions.

  • Context menus that steal OS-native copy/paste items.

Evidence

ProductImplementation
NotionAI actions on selected blocks via menu.
Arc / Chromium browsersSelection menus that send text to AI features.
Microsoft EdgeCompose and explain actions on page selections.
Google DocsHelp me write on highlighted text.

FAQ

What belongs in an AI context menu?

A short list of high-value actions for the selection type (rewrite, summarize, comment) plus a custom instruction entry.

How does this differ from magic edit?

Magic edit is the transform pattern itself. The context menu is the discovery surface that launches those transforms.

Should results open in chat or inline?

Prefer inline preview for edits; open chat when the user needs multi-turn follow-up.

Accessibility requirement?

Every mouse-only AI action needs a keyboard path and visible focus.