Step 01
Describe what you need
Use AI Assist to describe the kind of widget you want — an intake form, a status display, a confirmation control — in plain language.
Widgets
Responses worth acting on.
Widgets transform agent messages from text into interactive, structured interfaces. Forms, layouts, and controls — embedded directly in the thread, where the work is happening.
Thread · agent messagewidget embedded
finance agent
here is the request form ▍
widget · expense intake
Request typeReimbursementselect
Amount1,240.00input
CategoryTravelselect
cancelsubmit
structured inputcaptured
tool callinvoked
agent actioncontinues
The problem
Conversational interfaces stop short of real action.
A message is only useful when someone can act on it. Text alone leaves the last mile of every interaction to the person reading it.
The response should be where the work finishes, not where it restarts.
01
Text requires interpretation
When an agent returns a wall of text, users have to read it, parse it, and then act on it somewhere else. The response is a step, not a destination.
02
Inputs without structure
When agents need users to provide information, free-form conversation is inefficient. Structured input — fields, dropdowns, buttons — gets the right data, every time.
03
Actions that require another tool
When users have to copy information out of a thread and paste it into another system, the workflow breaks. The work should not leave the conversation.
What is a Widget
Interactive interfaces, built into every agent message.
A Widget is a rich, interactive component that an agent embeds directly into a thread message — replacing plain text with structured layouts users can read, fill in, and act on without leaving the conversation.
- 01
Component library
Widgets are built from a library of interface components. Combine fields, buttons, labels, and layouts to create the experience each agent and workflow requires.
- 02
AI Assist generation
Describe the widget you want in plain language. AI Assist generates the editable code and schema automatically — no building from scratch.
- 03
Interactive in the thread
Users see the widget as part of the agent's message and interact with it directly — filling in fields, clicking buttons — without opening another tool or leaving the conversation.
- 04
Actions from interactions
Interacting with a widget can invoke agent actions, including Tool calls. A button click or form submission triggers the agent to act on what the user provided.
Widget · anatomyai assist
"an intake form for feature requests"
generating code + schema
componentsschemaeditable code
widget · ready
agent · attachedin use
thread · renderedin use
tool · invokedin use
template · reusedin use
How it works
Describe it, refine it, deploy it.
Step 02
Review and refine
AI Assist generates the widget and its schema. Review and edit as needed to match your exact requirements.
Step 03
Attach to an agent
Attach the widget to an agent. The agent can now embed it into thread messages when the work calls for it.
Step 04
Users act in the thread
When the agent sends the widget, users interact with it right where the conversation is happening. Input is captured, actions are triggered, work moves forward.
Key benefits
From response to action, without switching tools.
Responses that invite action
Structured layouts, forms, and controls replace text-heavy replies — making it clear what a user needs to do and making it easy to do it right there.
Structured input, every time
When agents need information from users, widgets ensure that input arrives in the right format. No ambiguous free-text answers to interpret.
Built in minutes with AI Assist
Plain-language descriptions become working, editable widgets. Builders spend less time on interface code and more time on the work that matters.
Work stays in one place
Because widgets live in the thread, users provide input, trigger actions, and complete tasks in the same conversation — no context switching required.
See it in practice
From message to meaningful interaction.
Intake, reporting, and approvals — captured as structured input and acted on without leaving the conversation.
Case 01
Product
Product intake agent
A product manager wants their team to submit feature ideas and bug reports in a consistent format. Using AI Assist, they describe a simple intake form. Opal generates the widget. They attach it to their intake agent. When a teammate asks the agent to log an idea, the agent responds with the form in the thread — the teammate fills in the fields, submits, and the agent captures the structured details.
- Widget
- Feature and bug intake form
- Built with
- AI Assist, plain language
- Outcome
- No separate form tool
Case 02
Program Management
Status report collection
A program manager builds a weekly reporting agent that asks each team lead for a project update. Instead of parsing free-text answers, the agent sends a structured form with defined fields for status, blockers, and next steps. Every response arrives in the same format — ready to roll up into the weekly report.
- Widget
- Status · blockers · next steps
- Attached to
- Weekly reporting agent
- Outcome
- Uniform, roll-up ready responses
Case 03
Finance Ops
Request and approval flow
A finance operations team configures an agent that handles expense and reimbursement requests. When a team member requests a reimbursement, the agent sends a widget with the necessary fields. When the form is submitted, the agent triggers the approval Tool and confirms the submission — all within the thread.
- Widget
- Reimbursement request
- On submit
- Approval Tool invoked
- Outcome
- Completed inside the thread
Security and compliance
Interactive by design, governed by default.
01
Role-Based Access Control
Permissions control who can create, edit, and manage Widgets and attach them to agents.
02
Audit Log
Widget configuration and agent interactions are tracked in the platform's activity log.
03
Guardrails Enforcement
Guardrails apply to agent messages — including those that embed widgets — ensuring all outputs conform to policy.
04
Zero Data Retention
ZDR is enabled automatically for models and providers that support it, covering the intelligence that powers agent responses.
05
Certifications
ISO 27001, ISO 42001, and SOC 2 Type II certifications are underway.
Part of a complete platform
Widgets connect across Opal.
01AgentsWidgets are attached to agents — including Agent Templates — so agents embed them into thread messages and act on user input.02ThreadsWidgets are rendered and interacted with inside threads, where all real-time collaborative work happens.03ToolsWidget interactions — like button clicks or form submissions — can invoke Tool calls directly.04SpacesAgents with Widgets are deployed within Spaces, making interactive responses available to the right teams.05GuardrailsGuardrails apply to agent outputs including widget delivery, enforcing input and output policies.