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 for
React appsRich interactive tools using Chakra UI, Recharts, and Lucide icons as built-in component libraries
HTML appsCustom layouts, 3D and map visualizations, and anything that fits better as plain HTML/JS/CSS
Both types run in a sandboxed iframe and can read from and write to agent databases, load other documents, pull in libraries from public CDNs, generate and trigger file downloads (Excel, Word, ZIP, and more using standard CDN libraries), and call a curated set of agent tools — for example, HTTP requests through an API capability or queries against BigQuery, Snowflake, Notion databases, and similar data sources. Document and agent-database helpers on abundly (such as loadAgentDocument and queryDocumentData) use the same toolbox execution path as abundly.callTool with the matching tool names when the app runs in an agent context. The agent chooses the appropriate type based on your request, but you can tell it to use one or the other if you have a preference.

​
Multi-file apps

Simple apps live in a single document, but larger projects can be split across multiple files in a folder — for example, an index.html entry file alongside separate CSS, JavaScript, and image files. When a folder contains an entry file named index.html, index.jsx, or index.tsx, a Run app button appears directly on the folder row, letting you launch the whole folder as one app without navigating into it. Multi-file apps work across all document scopes — agent, workspace, team, and chat. Any folder with an entry file shows the Run app button, regardless of which library it lives in.
Ask the agent to “build this as a multi-file app in a folder” when you want a cleaner structure or when the app needs several supporting files.

​
How apps work

Interactive apps are shown alongside your other agent documents in the Documents view. When you open an app document, you use a mode selector:
  • View mode — The live rendered application (default view)
  • Text mode — The source code (React/JSX or HTML)
  • Changes mode — 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. When an app is open, a reload button re-runs it with the latest code, and a fullscreen button expands the preview to fill the window.

​
App scopes

Apps can live in multiple scopes depending on where they’re created:
ScopePersistenceBest for
Chat documentScoped to the current conversation; listed in the Chat Documents panelOne-off visualizations, quick prototypes, temporary tools
Agent documentSaved to the agent’s Documents panel, available outside the conversationReusable apps, apps you want to publish or share
Workspace / Team documentShared across the workspace or teamShared tools, team dashboards, cross-agent apps
When you ask the agent to create an app in a conversation, it creates a chat-scoped document and opens it in a side panel next to the chat. Follow-up edits keep the same document, so you can iterate without the panel re-rendering from scratch. You can browse everything created in the current chat by clicking the Chat documents button in the chat action bar. To keep an app around beyond the current conversation, promote it to an agent document:
  • Ask the agent: “Save this as an agent document”
  • Or open the document menu in the panel and choose Save as agent document
Once promoted, the app appears in your main Documents panel. You can open it anytime, the agent can reference it in any conversation, and it becomes eligible for publishing. Chat-scoped documents are automatically deleted when the chat is deleted.
Use chat documents 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
Publishing a database makes its entire contents publicly readable, regardless of which permissions you enable. The Read/Create/Update/Delete toggles control which operations public viewers can perform — they don’t hide rows. Anyone with the document link can fetch the full dataset, even if your app’s UI only displays a slice or aggregates. Only publish databases where every row is safe to share publicly.
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.
Apps that call agent tools (for example, HTTP requests through an API capability) work in the agent chat but not on public share links — the publish dialog warns you if this applies to your app.

​
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