Skip to main content

​
Overview

render_html lets the agent return rich desktop cards instead of plain Markdown. Use it for charts, tables, diagrams, compact dashboards, approval-like forms, or self-contained interactive views. Widgets are rendered in sandboxed iframes. They do not have network access, cannot load external scripts/styles/images/fonts, and should use inline CSS/JS only.

​
Modes

Use display for dashboards and visualizations. Use input for structured forms where the next agent step depends on user input.

​
Theming

The desktop app injects design tokens as CSS variables:
Prefer semantic HTML and the built-in widget styles for common controls: headings, paragraphs, tables, labels, inputs, buttons, .field, .grid-2, .chip, .actions, and .muted.

​
Input widgets

Submit exactly once with arden.submit({...}), or use arden.submitForm(form) for normal form collection.
The tool returns accept, decline, or cancel plus submitted values.

​
Constraints

  • Keep HTML fully self-contained.
  • Do not use external links, scripts, stylesheets, images, fonts, fetch/XHR, or form actions.
  • Use data: URIs for images if needed.
  • Do not draw your own outer card; the desktop app already supplies the card shell and title.