Table

table is display-only: a caption, 1–30 columns, and up to 1000 rows of scalar cells (string, number, boolean, null).

Live preview

Demos use docs host CSS. Package primitives are intentionally unstyled so your product theme owns the look.

When to use

• Compare options, list records, show structured tool results
• When markdown tables are too fragile for shells

Prefer something else when

• Interactive selection of a row → use choice-list with rows as choices
• Large free-form documents → markdown message content

Props (schema)

Frame example

{
  "protocol": "agentskit.chat.component",
  "version": 1,
  "type": "render",
  "componentKey": "table",
  "instanceId": "table-fixture",
  "props": {
    "caption": "Users",
    "columns": [
      { "key": "name", "label": "Name" },
      { "key": "role", "label": "Role" }
    ],
    "rows": [
      { "name": "Ada", "role": "Engineer" },
      { "name": "Grace", "role": "Operator" }
    ]
  },
  "fallback": {
    "kind": "table",
    "summary": "Users table with two rows."
  }
}

Events

No events. This key is display-only — do not invent host callbacks.

Host wiring

Display-only — register the component so the frame resolves; no interact handler is required.

import { TableComponent, defineComponentManifest, defineChat } from '@agentskit/chat'

const definition = defineChat({
  id: 'app',
  components: defineComponentManifest([TableComponent]),
  chat: { adapter },
})

For agents

Do not invent props or events outside the schema. Unknown keys and invalid props stay inert.

Shells

Related

• Source list — Citations not rows
• Catalog index — All keys
• Live lab — all components side-by-side