Skip to content
AlumiaDocs

Search docs

Find pages, headings, and concepts. Press ⌘K or Ctrl+K to toggle.

Blocks

Structured visual outputs for agent work on the canvas.

Open in ChatGPTOpen in Claude

Blocks are typed outputs that make agent work inspectable. Instead of leaving every result as plain chat text, Alumia renders structured displays through data blocks, connector-backed UIs through mcp-app blocks, explicit custom apps through artifact blocks, and a small set of show system primitives for documents, code, spreadsheets, browsers, terminals, timers, drawings, and chat transcripts.

How blocks are created

Agents use data_block for generated tables, charts, cards, maps, lists, dashboards, and other structured displays. Connector outputs become MCP Apps. The show tool is reserved for system primitives only. Each block is saved with typed data so it can be reopened, shared, and used as context later.

Why blocks matter

  • They keep long-running work visible.
  • They make artifacts easier to review than raw JSON.
  • They give agents a stable object to update instead of rewriting a whole conversation.

Use blocks when the output has structure, needs revision, or should remain visible after the chat moves on.