Cursor launches Live Apps: from a description to a shareable SSO URL
Cursor Build Live Apps scaffolds a web app, Postgres, SSO and hosting — then returns a shareable link. Available on all paid plans with cloud agents; security checks before publish.


Cursor now lets you build “live apps” inside the editor: describe what you need, and it scaffolds the web app, a Postgres database, Cursor SSO auth and hosting — then hands you a shareable link. The capability is available on all paid plans with cloud agents enabled.
The announcement came via Cursor’s official changelog and X account on Wednesday 5 November 2026. Cursor says agents have lowered the cost of writing code, but most apps and tools people build never leave localhost. Build Live Apps is meant to take a description all the way to a URL teammates can actually open.
From localhost to a shareable URL
According to Cursor, you start a cloud agent and explicitly say you want to build an app. The agent scaffolds the web app, spins up a Postgres database if needed, configures authentication behind Cursor SSO and provisions hosting. If the app must connect to your systems, such as a data warehouse, Cursor asks for the secrets it needs.
When you publish, you pick a unique domain and Cursor returns a live link. Cursor says people across sales, operations, legal, finance and engineering are already building internal apps — including event registration tools, multimedia customer presentations, onboarding experiences, sales pipeline dashboards and portals for engineering services.
Cursor can deploy apps from new or existing repos on Cursor Origin and GitHub. Support for other git providers such as GitLab is coming soon.
Security checks before anything goes live
On publish, Cursor runs deterministic and agentic security checks for common issues, such as secrets written into app files or exposed credentials. If a check fails, the agent tells you what to fix. Nothing goes live until the checks pass and you explicitly publish.
Team admins can see every app and secret on the team. They can also add their own rules to the security review, approve publishes the review blocked, and unpublish any app.
Sharing and access
Once checks pass, Cursor deploys the app to the URL you chose. You can share with specific people, groups or your entire team — behind Cursor sign-in. On individual plans, apps can also be shared publicly. Cursor also notes you can provision a Cursor API key if a script or Grok Bot should use your app.
Cursor says the capability is available now on all paid plans with cloud agents enabled. Update Cursor to try it.
Why it matters for leaders
- Internal tooling without the IT queue. When sales, ops and onboarding can describe a need and get a shareable SSO-backed app, ownership of “small systems” shifts. Leaders should decide who may publish and which data sources are allowed.
- Security is a product feature, not an appendix. Cursor blocks publish until checks pass — but team rules, approvals and unpublish sit with admins. Set policy before usage spreads.
- Secrets and integrations. Connecting a warehouse or other systems means someone supplies secrets. That is an IAM and audit question, not only a demo.
- Cost and plan requirements. Live apps need a paid plan with cloud agents. Budget for agent usage and hosting, and decide whether public sharing on individual plans is acceptable in your organisation.
- Competitive context. Cursor is positioning against “vibe coding” tools that stop at localhost or demos. For organisations already on Cursor, this is a concrete product step — not another model drop.
Sources and media
- Cursor: Build Live Apps in Cursor, 5 November 2026
- Cursor on X, 5 November 2026
Illustration: AI-generated with Grok Bot / hogby.ai