> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/editor/apps.md).

# FLORA Apps

FLORA Apps are small web apps your AI agent builds and publishes to your workspace. Find them in the Library, share them, track how they're used, and open them in an agent to change them.

A FLORA App is a web page an AI agent builds for you and publishes to FLORA: a product picker, a campaign brief form, a review board or any other small tool your team uses. Ask your agent (Claude, ChatGPT, Cursor or another client connected through [FLORA MCP](https://docs.flora.ai/mcp.md)) to build one, and it appears in your workspace's Library. Apps can read FLORA data as the person viewing them, start generations when a viewer clicks, and keep shared data such as votes or form entries.

FLORA Apps are available in every workspace.

## Find your apps

Hover **Library** in the dashboard sidebar and choose **Apps**. The list shows the apps your team has published. Filter it with **All**, **Private**, **Workspace** and **External**, or use **Search apps**.

If the workspace has no apps yet, the empty state offers starter prompts. Choose **Send to your agent** to hand one to your connected agent.

Click an app to open its details page:

* **Access** — who can open the app.
* **Versions** — every published version of the app.
* **Insights** — who opens the app and what they make with it.
* **Generations** — the generations people started from the app.

Choose **Open** to run the app in a new tab.

## Share an app

Open the app and choose **Share**. Under **Who can open it**, pick one of:

| Option                            | Who can open it                                                                |
| --------------------------------- | ------------------------------------------------------------------------------ |
| **Private**                       | Only you, and people you invite by email.                                      |
| **Only {workspace}**              | Members of this workspace.                                                     |
| **People in your organization**   | Signed-in members of your organization who have the link.                      |
| **Anyone on FLORA with the link** | Anyone signed in to FLORA who has the link. Others are asked to sign in first. |

For link sharing, choose what people with the link can do: **Can view**, or **Can edit data** to also change the app's saved data. Choose **Copy link** to copy the app's address.

## Change an app with your agent

In the app's top bar, open **Open in Agent** next to **Share** and pick an agent, such as Claude, Claude Code, ChatGPT, Codex or Cursor, or copy the prompt. FLORA hands the agent a prompt that points it at this app, so it can edit it if you manage the app, or remix it into a new one if you don't. Visitors who aren't signed in see a sign-in link instead.

## Plan limits

A Free workspace can have **2 live apps**. Updating an app doesn't count as a new one, and deleting an app frees a slot. At the limit, publishing a new app is refused until you delete one or upgrade. Paid plans have no app limit. See [How FLORA pricing works](https://docs.flora.ai/plans-and-billing/pricing.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/editor/apps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
