Skip to main content
Message presentation is OpenClaw’s shared contract for rich outbound chat UI. It lets agents, CLI commands, approval flows, and plugins describe the message intent once, while each channel plugin renders the best native shape it can. Use presentation for portable message UI: text sections, small context/footer text, dividers, charts, tables, buttons, select menus, and card title/tone. Do not add new provider-native fields such as Discord components, Slack blocks, Telegram buttons, Teams card, or Feishu card to the shared message tool. Those are renderer outputs owned by the channel plugin.

​
Contract

Plugin authors import the public contract from:
Shape:
Button semantics:
  • action.type: "command" runs a native slash command through core’s command path. Use this for built-in command buttons and menus.
  • action.type: "callback" carries opaque plugin data through the channel’s interaction path. Channel plugins must not reinterpret callback data as slash commands.
  • action.type: "approval" identifies one durable operator approval, its explicit exec or plugin kind, and the requested decision. Channel plugins encode that action into a transport-private callback and resolve it through the approval service; they must not parse /approve command text or infer kind from the ID.
  • action.type: "url" opens a normal link.
  • action.type: "web-app" launches a channel-native web app.
  • value is the legacy opaque callback value. New controls should use action so channel plugins can map commands and callbacks without guessing from text.
  • url, webApp, and web_app remain accepted as deprecated boundary inputs. Normalizers preserve these fields so renderers can distinguish shipped legacy semantics from explicit typed actions. New producers should use action.
  • label is required and is also used in text fallback.
  • style is advisory. Renderers should map unsupported styles to a safe default, not fail the send.
  • priority is optional. When a channel advertises action limits and controls must be dropped, core keeps higher-priority buttons first and preserves original order among equal priority buttons. When all controls fit, authored order is preserved.
  • disabled is optional. Channels must opt in with supportsDisabled; otherwise core degrades the disabled control to non-interactive fallback text. A disabled button always renders label-only in fallback text, even when it carries a command action.
  • reusable is optional. Channels that support reusable native callbacks may keep the action available after a successful interaction. Use it for repeatable or idempotent actions such as refresh, inspect, or more details; leave it unset for normal one-shot approvals and destructive actions.
Select semantics:
  • options[].action accepts only command or callback; approval and link actions are button-only.
  • options[].value is the legacy selected application value.
  • placeholder is advisory and may be ignored by channels without native select support.
  • If a channel does not support selects, fallback text lists the labels.
Chart semantics:
  • pie requires positive segment values.
  • bar, area, and line use one ordered categories array. Every series supplies exactly one finite value per category, in the same order.
  • Category labels and series names must be unique. Invalid or incomplete chart blocks are dropped during normalization rather than silently changing data.
  • Native chart rendering is opt-in through presentationCapabilities.charts. Other channels receive the chart title, axes, categories, series, and values as deterministic text. This is also the accessibility fallback.
Table semantics:
  • caption is a required short heading. headers must contain at least one unique, non-empty column label.
  • rows must contain at least one row. Every row must have exactly one cell per header, and every cell must be a non-empty string or a finite number.
  • rowHeaderColumnIndex is an optional zero-based index identifying the column whose cells should be exposed as row headers by native renderers.
  • Table normalization is atomic. An invalid caption, header, row width, cell, or row-header index drops the table block instead of truncating or repairing its data.
  • Native table rendering is opt-in through presentationCapabilities.tables. Other channels receive the caption and every row as deterministic linear text, with internal whitespace collapsed:
There is no separate report discriminator. Compose a report from title, tone, text, context, chart, table, and action blocks. This keeps each block independently renderable and gives the complete report the same deterministic text fallback.

​
Producer examples

Simple card:
URL-only link button:
Telegram Mini App button:
Select menu:
Chart:
Table report:
CLI send:
Pinned delivery:
Pinned delivery with explicit JSON:

​
Renderer contract

Channel plugins declare render support on their outbound adapter:
Capability booleans describe what the renderer can make interactive. Optional limits describe the generic envelope core can adapt before calling the renderer:
Core applies generic limits to semantic controls before rendering. Renderers still own final provider-specific validation and clipping for native block count, card size, URL limits, and provider quirks that cannot be expressed in the generic contract. If limits remove every control from a block, core keeps the labels as non-interactive context text so the delivered message still has a visible fallback.

​
Core render flow

On the canonical outbound path used by CLI and standard message actions, core:
  1. Normalizes the presentation payload.
  2. Resolves the target channel’s outbound adapter.
  3. Reads presentationCapabilities.
  4. Applies generic capability limits such as action count, label length, and select option count when the adapter advertises them. Chart and table blocks become deterministic text unless the adapter explicitly advertises charts: true or tables: true, respectively.
  5. Calls renderPresentation when the adapter can render the payload.
  6. Falls back to conservative text when the adapter is absent or cannot render.
  7. Sends the resulting payload through the normal channel delivery path.
  8. Applies delivery metadata such as delivery.pin after the first successful sent message.
Channel-local reply or preview funnels that consume ReplyPayload directly must either enter that canonical path or materialize the same presentation fallback before projecting the payload down to plain text/media. Core owns fallback behavior so producers can stay channel-agnostic. Channel plugins own native rendering and interaction handling.

​
Degradation rules

Presentation must be safe to send on limited channels. Fallback text includes:
  • title as the first line
  • text blocks as normal paragraphs
  • context blocks as compact context lines
  • divider blocks as a visual separator
  • button labels, including URLs for link buttons
  • select option labels
  • chart title, type, axes, categories, series, and values
  • table caption, headers, and every row value

​
Button value fallback visibility

When a channel cannot render interactive controls, button and select values fall back to plain text. The fallback behavior preserves usability while keeping opaque callback data private:
  • command-typed actions render as label: `command` so users can copy the command and run it manually in the channel input.
  • callback-typed actions and legacy value fields render as label-only. The opaque callback value is not exposed in fallback text.
  • approval-typed actions render label-only. Approval IDs and decisions are transport data and are not exposed through generic scalar helpers or fallback text.
  • url / web-app actions and deprecated url / webApp / web_app inputs render the URL text alongside the button label, since the URL is user-facing.
  • Select options render as label-only. The underlying option value is not exposed in fallback text.
Channel adapters that add manual-command guidance in their fallback UI (e.g. Feishu document-comment instructions) must derive the command-present check from the same presentation blocks that the fallback renderer uses, so the guidance text only appears when a manual command is actually shown. Unsupported native controls should degrade rather than fail the whole send. Examples:
  • Telegram with inline buttons disabled sends text fallback.
  • A channel without select support lists select options as text.
  • A channel without native chart support lists the chart data as text.
  • A channel without native table support lists every table row as text.
  • A URL-only button becomes either a native link button or a fallback URL line.
  • Optional pin failures do not fail the delivered message.
The main exception is delivery.pin.required: true; if pinning is requested as required and the channel cannot pin the sent message, delivery reports failure.

​
Provider mapping

Current bundled renderers: Provider-native payload compatibility is a transition affordance for existing reply producers. It is not a reason to add new shared native fields.

​
Presentation vs InteractiveReply

InteractiveReply is the older internal subset used by approval and interaction helpers. It supports:
  • text
  • buttons
  • selects
MessagePresentation is the canonical shared send contract. It adds:
  • title
  • tone
  • context
  • divider
  • chart
  • table
  • URL-only buttons
  • generic delivery metadata through ReplyPayload.delivery
Use helpers from openclaw/plugin-sdk/interactive-runtime when bridging older code:
New code should accept or produce MessagePresentation directly. Existing interactive payloads are a deprecated subset of presentation; runtime support remains for older producers. Non-deprecated helpers worth knowing:
  • normalizeMessagePresentation(raw) / hasMessagePresentationBlocks(value) validate and coerce an untyped payload (for example, JSON from the CLI --presentation flag) into MessagePresentation.
  • isMessagePresentationInteractiveBlock(block) narrows a block to the buttons | select union.
  • resolveMessagePresentationButtonAction(button) and resolveMessagePresentationOptionAction(option) return the canonical typed action while accepting deprecated boundary fields. An explicit action always wins.
  • resolveMessagePresentationActionValue(action) / resolveMessagePresentationControlValue(control) read command/callback scalar values only. A non-scalar canonical action never falls through to a legacy shadow value, so approval IDs and link targets stay typed.
  • renderMessagePresentationChartFallbackText(block) / renderMessagePresentationTableFallbackText(block) render one structured data block as deterministic text for channel-specific fallback paths.
The legacy InteractiveReply* types and conversion helpers are marked @deprecated in the SDK:
  • InteractiveReply, InteractiveReplyBlock, InteractiveReplyButton, InteractiveReplyOption, InteractiveReplySelectBlock, and InteractiveReplyTextBlock
  • normalizeInteractiveReply(...)
  • hasInteractiveReplyBlocks(...)
  • interactiveReplyToPresentation(...)
  • presentationToInteractiveReply(...)
  • presentationToInteractiveControlsReply(...)
  • resolveInteractiveTextFallback(...)
  • reduceInteractiveReply(...)
presentationToInteractiveReply(...) and presentationToInteractiveControlsReply(...) remain available as renderer bridges for legacy channel implementations. New producer code should not call them; send presentation and let core/channel adaptation handle rendering. Approval helpers also have presentation-first replacements:
  • use buildApprovalPresentationFromActionDescriptors(...) instead of buildApprovalInteractiveReplyFromActionDescriptors(...)
  • use buildApprovalPresentation(...) instead of buildApprovalInteractiveReply(...)
  • use buildExecApprovalPresentation(...) instead of buildExecApprovalInteractiveReply(...)
Those shipped builders remain command-backed for plugin compatibility. Gateway and bundled channel code that owns a durable approval kind should use buildTypedApprovalPresentation(...), buildTypedExecApprovalPendingReplyPayload(...), or buildTypedPluginApprovalPendingReplyPayload(...) so transports receive an explicit approval action instead of inferring semantics from /approve text. renderMessagePresentationFallbackText(...) returns an empty string for presentation blocks that have no text fallback, such as a divider-only presentation. Transports that require a non-empty send body can pass emptyFallback to opt into a minimal body without changing the default fallback contract.

​
Delivery pin

Pinning is delivery behavior, not presentation. Use delivery.pin instead of provider-native fields such as channelData.telegram.pin. Semantics:
  • pin: true pins the first successfully delivered message.
  • pin.notify defaults to false.
  • pin.required defaults to false.
  • Optional pin failures degrade and leave the sent message intact.
  • Required pin failures fail delivery.
  • Chunked messages pin the first delivered chunk, not the tail chunk.
Manual pin, unpin, and pins message actions still exist for existing messages where the provider supports those operations.

​
Plugin author checklist

  • Declare presentation from describeMessageTool(...) when the channel can render or safely degrade semantic presentation.
  • Add presentationCapabilities to the runtime outbound adapter.
  • Implement renderPresentation in runtime code, not control-plane plugin setup code.
  • Keep native UI libraries out of hot setup/catalog paths.
  • Declare generic capability limits on presentationCapabilities.limits when they are known.
  • Preserve final platform limits in the renderer and tests.
  • Add fallback tests for unsupported charts, tables, buttons, selects, URL buttons, title/text duplication, and mixed message plus presentation sends.
  • Add delivery pin support through deliveryCapabilities.pin and pinDeliveredMessage only when the provider can pin the sent message id.
  • Do not expose new provider-native card/block/component/button fields through the shared message action schema.