The registration tool works on your computer. Now somebody else needs to use it. Cursor’s new live-app workflow tackles that handover: its cloud agent can build an app, arrange a database and authentication, then host it at a link you can share.

Based on 4 reviewed sources · See sources

The link comes after a publishing decision

Cursor’s 5 November announcement describes a path from a request to a hosted app, with an optional Postgres database—a place to store the app’s records—and sign-in controls. Cursor says its own teams already use the workflow for event registration, account assignments and other internal tools. Those are company examples, not an independent adoption count.

The documentation separates the preview from publishing: the person chooses when to publish, and the app must pass checks for exposed credentials and other configured rules first. Team administrators can add review requirements, inspect apps and unpublish them. These controls describe a publishing gate; they are not evidence that every generated app is secure.

Cursor’s original demonstration shows the proposed handover below. The relevant change is getting a tool to its next user, beyond producing code.

From the source · Cursor ·

Cursor demonstrates building and deploying a live app with a shareable link.

View the original post on X ↗

Sharing and access still need checking

The feature requires a paid plan with cloud-agent access and does not work with local agents. Team apps can use Cursor sign-in; public sharing is off by default for Teams and Enterprise unless an administrator enables it. Individual accounts can share publicly.

Availability is also reaching accounts gradually. In a support thread about a missing Apps page and publish control, Cursor staff member Mohit explained on 5 November that the rollout was still in progress and the documentation was ahead of some accounts.

The inspected announcement and app guide do not specify a separate hosting tariff or a European hosting region. Those details remain unanswered for anyone choosing where to put a customer-facing tool.

Sources

Written with AI assistance from the sources above. Analysis and practical implications are our interpretation. Our editorial approach.