Agent work

To-do list

A stable-ID checklist for plans that change while an agent works.

To-do list — 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 234 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: TodoList
Source: todo_list.rs
Story: todos
Demo height: 234 px
Events: TodoListEvent

Code

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

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

TodoList::new("plan")
    .title("Supplier switch plan")
    .items([
        TodoItem::new("contract-terms", "Pull current contract terms").done(),
        TodoItem::new("compare-prices", "Compare Q3 unit prices").done(),
        TodoItem::new("draft-timeline", "Draft transition timeline")
            .status(TodoStatus::Active),
        TodoItem::new("cold-chain", "Confirm cold-chain capacity"),
        TodoItem::new("confirm-orders", "Send order confirmations"),
    ])
    .on_event(cx.listener(|_, event: &TodoListEvent, _, _| {
        println!("todo event: {event:?}");
    }))

Events and ownership

Who owns the state: TodoList renders state supplied by the application; it does not own durable work.
What it emits: Interactive intent is reported through the typed TodoListEvent contract and stable application IDs.
What it means: A stable-ID checklist for plans that change while an agent works.
Overflow and motion: Wide content retains context in a bounded surface; reduced motion preserves a useful state.

Event types

TodoListEvent

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.