Apps
Package your Agents and Flows into one product, fronted by a Supervisor that routes every request to the right piece and answers with one voice.
Apps
An App packages the pieces you've already built - Agents and Flows - into one product. Every App is headed by a Supervisor: an Agent you choose that fronts the whole thing, decides when to answer itself and when to hand work to a specialist, and synthesizes the result. The person on the other end talks to one assistant the entire time.
Think of an App as:
- A business coach whose Supervisor chats freely, but runs your scoring Flow when someone asks for a diagnostic and hands pricing questions to your pricing Agent.
- A client portal product - one link that bundles everything a client engagement needs behind a single front door.
- An API product - a typed, machine-callable service assembled from your existing building blocks.
Apps live at the top of the sidebar's Build group and are available on every plan.
App or Suite?
Both package what you build, but differently:
| If you want to... | Use a(n)... |
|---|---|
| One assistant that orchestrates several Agents and Flows behind a single conversation | App |
| A catalog page where people browse and open each Flow or Agent themselves | Suite |
| Sell or share one coherent product with one entry point | App |
| Bundle many items (including Apps) for an audience | Suite |
They compose: an App can sit inside a Suite like any other item, and a published App can be a Portal's New chat assistant.
How an App is put together
- The Supervisor - an Agent from your workspace. Swappable at any time: drag a different Agent onto the Supervisor slot. Each App also carries its own orchestration and synthesis instructions, stored on the App - the same Agent can lead two Apps and behave differently in each.
- The Orchestrates band - the Agents and Flows the Supervisor can route work to. Members are live references, not copies: improve an Agent once and every App using it improves too.
- Orchestration mode - what the Supervisor may call: Agents only, Flows only, both, or nothing (Supervisor answers alone).
- Goals - App-level outcomes layered into the Supervisor's instructions at run time.
Drafts are live, published versions are pinned
While you're composing, everything is live - the canvas and the preview chat always use the latest version of every member. Publishing pins: the Supervisor and every orchestrated member are frozen at their current published versions, so an App your users rely on never changes silently. Republishing a member does not update a published App - republish the App to pick up new member versions.
Publishing requires the Supervisor and every orchestrated member to be published first; the Mode tab lists anything that still needs publishing.
Where Apps run
- The editor preview - a live chat wired to the draft composition.
- Share links - a published App has a public page like any Flow.
- Suites and Portals - add an App wherever you'd add a Flow, including as a Portal's New chat assistant.
- The External API - every published App can expose a Conversation Service and a Transaction Service for your own systems.
Wherever an App is shared or embedded, the opening page or link can pass details about the visitor to the Supervisor and every member. See Session context.