Readable output

Selection actions

Ask, explain, and rewrite actions anchored to selected Markdown.

Selection actions — gpui-ai

Starts when it scrolls into view

NORD FROST · DARK · RADIUS 6/10 · BASE 16PX · SHADOW

Running the real component, compiled to WebAssembly. The frame is 288 px tall, which is what this story measures at the demo width in the default type size — a narrower column or a theme that changes that size will wrap it differently.

Type: SelectionActions
Source: selection_actions.rs
Story: selection-actions
Demo height: 288 px
Events: SelectionActionsEvent

Code

Cut from the gallery story this page runs, so it stays true.

crates/gallery/src/gallery.rsOpen in the gallery Implementation

SelectionActions::new(
    "gallery-selection-actions",
    "## Weekly flavor review\n\nMint Chip demand softened while Vanilla recovered. Select any phrase in this readable analysis, then choose an action. Native **Ctrl/Cmd+A** and copy remain available.",
    window,
    cx,
)

Events and ownership

Who owns the state: SelectionActions renders state supplied by the application; it does not own durable work.
What it emits: Interactive intent is reported through the typed SelectionActionsEvent contract and stable application IDs.
What it means: Ask, explain, and rewrite actions anchored to selected Markdown.
Overflow and motion: Wide content retains context in a bounded surface; reduced motion preserves a useful state.

Event types

SelectionActionsEvent

What the demo does and does not show

The demo above is the same Rust as the native component, compiled to WebAssembly and drawn on a WebGPU canvas — not a mock-up, a recording, or a re-implementation. What it paints is what the component paints: layout, colour from the live theme, and motion.

The live browser specimen requires WebGPU; the native component remains the authoritative runtime.

A canvas cannot stand in for the platform, so treat everything that goes through the operating system as unproven here: keyboard handling and shortcuts, screen reader semantics, text input and IME, the clipboard, file drops, and the frame rate you would get on your own GPU. Judge those in a native build. If your browser has no WebGPU, the frame says so rather than showing an empty box.