Skip to main content
Apps are agent documents containing executable code that renders as a user interface. Ask your agent to create a dashboard, form, or custom tool, and it writes the code and displays the result. You can see and tweak the code yourself, or ask the agent to make changes.
Feedback Hub dashboard aggregating customer feedback from Twitter, Email, Survey, App Review, and Support Calls—showing sentiment trends, key metrics, and a live feed of categorized feedback

​
Two types of apps

Agents can create two types of applications:
TypeBest forCapabilities
React appsInteractive tools, data-driven dashboards, forms that write to databasesFull interactivity, database access, state management, component libraries
HTML documentsStatic reports, styled content, simple visualizationsLightweight, no dependencies, good for embedding or sharing
The agent chooses the appropriate type based on your request, but if you have a preference you can just tell it to use one or the other.

​
How apps work

Interactive apps are shown alongside you other agent documents in the Documents view. When you open an app document, you see three tabs:
  • Text tab — The source code (React/JSX or HTML)
  • Preview tab — The live rendered application (default view)
  • Changes tab — A history of all changes made to the app
You can edit code directly or ask the agent to make changes. Every edit is versioned automatically.

​
Chat artifacts vs agent documents

Apps can live in two places, which sometimes causes confusion:
LocationPersistenceBest for
Chat artifactLives only in the conversation, shown in the side panelOne-off visualizations, quick prototypes, temporary tools
Agent documentSaved to the Documents panel, available outside the conversationReusable apps, apps you want to publish or share
When you ask the agent to create an app in a conversation, it typically appears as a chat artifact—rendered in a panel to the right of the chat. This is convenient for quick iterations, but the app only exists within that conversation. Each time the agent makes changes, it rewrites the entire artifact. To keep an app around, save it as an agent document:
  • Ask the agent: “Save this as an agent document”
  • Or click the menu icon in the artifact panel and choose Save as agent document
Once saved, the app appears in your Documents panel. You can open it anytime, and the agent can show it in any conversation when relevant. Only agent documents can be published—chat artifacts cannot.
Use chat artifacts for exploratory work: “Show me a chart of last month’s sales.” When you have something worth keeping, save it as an agent document.

​
Publishing apps with data

Like other agent documents, apps can be published with a public URL. Anyone with the link can view and interact with the app. If your app reads from an agent database, you need to publish that database too—otherwise the app won’t have data to display. When publishing a database, you choose what public viewers can do:
Publish Document dialog showing permission checkboxes: Read (checked), Create, Update, and Delete operations for public viewers
PermissionWhat it allows
ReadView data (required for dashboards and data displays)
CreateSubmit new records (enable for public forms)
UpdateModify existing records
DeleteRemove records
For a public feedback form, publish both the app and the database. Enable Read and Create on the database so visitors can submit entries. Leave Update and Delete disabled unless you want the public to modify existing data.

​
Typical use cases

Dashboards and data browsers
  • Sales metrics with filters by region and date
  • Project status boards showing tasks by stage
  • Inventory views with search and category filtering
Data collection
  • Customer feedback forms
  • Event registration
  • Order intake forms that write to a database
Internal tools
  • Approval workflows with action buttons
  • Scheduling views with drag-and-drop
  • Comparison tools for evaluating options
Public utilities
  • Pricing calculators for your website
  • Quote generators for sales teams
  • Interactive reports for clients

​
Real-world example

A TV production company used Abundly to build a photographer scheduling system. The agent created its own database and interactive dashboard for visualizing and managing schedules. Staff could view the schedule, and the agent could suggest and apply changes through conversation.
Screenshot of the SVT Scheduler Agent dashboard

Behind the Scenes: Making a Scheduler Agent for SVT

Full case study showing how the agent built its own database and dashboard for a real production workflow

​
Learn more

Agent Databases

The data layer that powers interactive apps

Agent Documents

How apps fit into the document system

Code Execution and Scripts

Code that runs for processing and automation