Cursor's Build Live Apps Turns a Text Prompt Into a Hosted Web App

Cursor has released Build Live Apps , a cloud-agent workflow that turns a natural-language request into a hosted web application. The agent can generate the code, provision Postgres, add authentication through Cursor SSO, run security checks, and return a shareable URL.

A usable internal app requires more than generated code. It also needs hosting, identity, data storage, secrets, and deployment controls. Cursor now manages those components for supported web apps, giving developers and other teams a shorter path from prototype to working service.

A four-step path to a live URL

Developers start a cloud agent from a new or existing repository and explicitly ask it to build an app. Repositories can be hosted on Cursor Origin or GitHub, while GitLab support is planned for a later release.

1. Describe the app. The developer provides the requirements in natural language.
2. Generate the project. The agent scaffolds the web app and writes the application code.
3. Provision services. Cursor can create a Postgres database, configure Cursor SSO, set up hosting, and request credentials for external systems.
4. Review and publish. After security checks pass, the developer selects a unique domain and publishes the app.

Credentials are collected through explicit prompts when an app needs access to a warehouse, API, or internal service. Team apps open behind Cursor sign-in, and publication requires a separate action from the developer.

Security checks can block a release

Before an app goes live, Cursor runs deterministic checks based on fixed rules and agentic checks that inspect the project with an AI agent. The review looks for problems such as secrets stored in application files and exposed credentials. A failed check blocks publication and gives the agent an opportunity to correct the issue.

Team administrators receive an inventory of apps and secrets across the organization. They can add review rules, approve a publication that a rule blocked, and unpublish an existing app. These controls give organizations a central approval and shutdown mechanism for tools created outside a traditional engineering workflow.

Small internal apps lead the use cases

Cursor says its sales, operations, legal, finance, and engineering teams are already using the workflow. The examples focus on practical tools with limited audiences:

• Event registration, account assignment, and desk-seating tools
• Customer presentations that combine slides, video, and interactive demos
• Training and onboarding applications
• Live sales-pipeline dashboards
• Portals for managing engineering services

These projects may serve only a small group, yet they still require reliable hosting, access control, and persistent data. Automating that infrastructure reduces the maintenance burden that often leaves internal prototypes stranded on a developer's machine.

Sharing follows the audience

Teams can grant access to specific people, selected groups, or the entire organization through Cursor sign-in. Individual-plan users can also publish apps for public access.

Cursor API keys provide programmatic access for scripts and bots. That allows a generated app to participate in a larger automation, such as receiving data from another service or exposing a workflow to an internal bot.

Deployment joins Cursor's agent stack

Build Live Apps extends Cursor's cloud agents from code generation through hosted deployment. The related Agent SDK lets developers define an agent as a folder of code and deploy it, while cloud-agent environments now support as many as 300 repositories. Cursor also says those environments load faster.

The combined tooling supports a broader workflow inside Cursor: agents can write code, connect managed services, pass release checks, and operate as running applications or automated services.

Where the managed workflow stops

Cursor's current deployment path targets web apps that fit its Postgres, SSO, and managed-hosting model. Projects requiring custom networking, another identity system, specialized infrastructure, or a different backend architecture still need a conventional deployment pipeline. GitLab support remains planned, with no release date announced.

Access on paid plans

Build Live Apps is available on all paid Cursor plans with cloud agents enabled. Users need the latest Cursor release, then can start a cloud agent and ask it to build an app. Setup instructions and supported behavior are covered in the app documentation .