generative-ui

Generative UI panels

present_ui displays a static, allowlisted, no-code panel. Call it directly; it is not a widget or an app.

Choose the smallest surface

Need	Use
An explanation, conclusion, or short list	Plain prose
A small comparison that reads well as text and needs no visual grouping	A markdown table
Information already in hand that benefits from status, cards, grouped fields, or a compact visual summary	present_ui
A chart, interactive controls, or a custom interactive display	Delegate to st-widget-builder; its Streamlit widget runs code in a browser sandbox
A durable surface with its own data and pipelines	Delegate to app-builder

A panel lays out known information with fixed components. It does not fetch data, run code, accept input, or become a durable application.

The call

Three arguments, all top level. root is a list; there is no wrapper object around it.

{
  "summary": "Release checks for main",
  "root": [
    {"component": "Heading", "value": "Release checks", "level": 2},
    {
      "component": "Card",
      "title": "Current status",
      "children": [
        {"component": "Badge", "label": "Ready", "status": "success"},
        {
          "component": "KeyValue",
          "items": [
            {"label": "Tests", "value": "Passed"},
            {"label": "Review", "value": "Complete"}
          ]
        },
        {"component": "Alert", "body": "No remaining blockers.", "variant": "info"}
      ]
    }
  ]
}

Every node is flat: component names the type, and that type's fields sit beside it on the same object. Only Card and Stack accept children.

Component vocabulary

The present_ui description carries it, flat, and that copy is the only one. It is derived from the same models that validate your call, so it lists every component with its required and optional fields and cannot be out of date. Read it there rather than expecting a list here — a second copy in this file could only ever be older.