Interactive Apps

Documentation Index

Fetch the complete documentation index at: https://docs.abundly.ai/llms.txt

Use this file to discover all available pages before exploring further.

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.

​

Two types of apps

Agents can create two types of applications: 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. 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 on the folder card, letting you launch the whole folder as one app.

​

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.

​

Chat documents vs agent documents

Apps are always agent documents, but they can live in two scopes: 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.

​

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:

​

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.

​

Learn more