Playbooks · Coding tasks
Cursor builds live apps from cloud agents
Written November 7, 2026
Cursor's Build Live Apps (Nov 5) lets a cloud agent scaffold a web app, add Postgres and SSO auth, and deploy it to a link. What ships — and what needs you.
What shipped
Build Live Apps in Cursor, in the November 5 changelog, starts from a plain observation: agents lowered the cost of writing code, but most apps and tools people build never make it off localhost. Now you can build live apps directly in Cursor and share them with a link. Kick off a cloud agent, tell it explicitly you want to build an app, and Cursor scaffolds the web app, spins up a Postgres database if needed, sets up authentication behind Cursor SSO, and provisions hosting. When you publish, you pick a unique domain and get back a live link.
Cursor can deploy apps from new or existing repos across Cursor Origin and GitHub. Support for other git providers such as GitLab is coming soon. The capability is available on all paid plans with cloud agents enabled — cloud agents only, not local agents, and not on free plans. On individual plans, cloud agents start with the $30-a-month Premium plan, which lists cloud agents and automations among its features; the $8 Plus plan covers Grok models only.
The publish gate
Building is not publishing. When you publish an app, Cursor runs deterministic and agentic security checks to catch common issues, such as secrets written into app files or exposed credentials. If a check fails, the agent tells you what it needs to fix. Nothing goes live until the checks pass and you explicitly publish the app.
Four checks run before every publish and stay on even when the broader security review is off: no secrets written into app files, no credential files, no .env files, and no source maps. On top of them, an AI review reads the files and blocks serious issues. Team admins can see every app and secret on the team, add their own rules to the security review, approve publishes the review blocked, and unpublish any app.
If the app needs to connect to your systems — Cursor's example is a data warehouse — Cursor asks for the secrets it needs, and the agent never sees the values. The secrets go through Cursor's Apps secrets system, usually entered by a team admin in the Apps dashboard.
What it is for
Cursor describes internal tools as the use case: anyone in an org can build useful tools for their work and share them with teammates. Its own examples are internal ops tools for event registration, account assignments, and desk seating; live dashboards for sales teams; and portals to manage engineering services. Once the checks pass, you share the app with specific people, groups, or your whole team, all behind Cursor sign-in. On individual plans, you can also share apps publicly.
The gaps
Cursor publishes no hosting price, no usage quota, no per-app fee, and no hostname pattern for live apps. There is nothing to budget against yet beyond the paid plan itself. And the flow still needs you at two points: you have to tell the cloud agent explicitly that you want an app, and you have to publish it yourself. The agent scaffolds and deploys; the decision to go live stays with a person.
Limits
- Nothing here reports a live app deployed through a cloud agent. The flow, the publish checks, and the gaps above come from Cursor's changelog and Apps docs.
- A publish run needs a paid Cursor plan with cloud agents enabled. That is the step this page does not cover from experience.
- The four always-on checks are listed in Cursor's Apps docs. The changelog itself describes the checks in general terms; the enumeration comes from the docs behind it.
Related playbooks
- Antigravity's remote agents run in Google's cloud
- Cursor agents take voice calls now
- Hand a task to a Cline cloud agent
- MOSS-Live: full-duplex spoken AI
Sources
Back to: Coding playbooks hub · Also: Hand a task to a Cline cloud agent · GitHub Agentic Workflows are now GA · Move Cursor work before the OpenAI shutoff