Cursor on 5 November 2026 launched Live Apps, a cloud-agent workflow that scaffolds a web app, can provision Postgres, puts private and team apps behind Cursor SSO, hosts the result and returns a live link only after the user explicitly publishes, according to the Cursor changelog and Cloud Agent apps documentation. Cursor says the capability is available on all paid plans with cloud agents enabled.
The company describes a build-then-gate path: the agent prepares the app, the user previews it in a tray, picks a domain at publish time, and Cursor runs deterministic and agentic security checks before anything is live. If checks fail, the agent lists fixes; nothing deploys until those pass and the user chooses to publish.
What Cursor says Live Apps include
Cursor says cloud agents can deploy from new or existing repos on Cursor Origin and GitHub, and that support for other git providers such as GitLab is “coming soon.” Hosting sits in a dedicated account Cursor creates for the team or for an individual plan user, isolated from other teams. If the app needs a database, Cursor provisions Postgres automatically. Secrets for warehouses or other systems are prompted for; Cursor says the agent never sees the secret values, with team admins typically creating team secrets in the Apps dashboard.
Sharing modes cover invited people, the whole Cursor team, or public links. Public sharing is off by default for Teams and Enterprise; a team admin can enable it. Individuals can share publicly without Cursor auth. Team admins can see every team app and secret, add custom security-review rules, approve publishes that the review blocked, and unpublish any app. Docs also describe Cursor API keys (personal or team) in an x-cursor-app-token header so Grok Bot, scripts or CI can call private or team apps the way a signed-in user would.
How Live Apps differ from Cursor’s other agent surfaces
TSN has covered Cursor desktop computer use, the Cursor Agent SDK, and the Origin app marketplace. Computer use drives local desktop apps; the Agent SDK packages agents as code; Origin’s marketplace lists partner apps on the host. Live Apps are a separate cloud build-and-host path for shareable web apps — not a fold-in to the desktop computer-use post.
That separation matters for readers who saw computer-use coverage and might assume Live Apps are the same agent controlling a local GUI. Cursor’s own docs put Live Apps on hosted URLs, Postgres and SSO, with an explicit human publish step after security review.
What an explicit-publish cloud app loop changes for teams
On Cursor’s terms, the operational change is a shorter path from a natural-language app request to a hosted URL that teammates can open — still gated by paid cloud agents, security checks and a human publish click. Secrets stay out of the agent’s view in the documented flow, and Teams/Enterprise keep public sharing off unless an admin flips it, which is a clearer default than an always-public preview link.
For individual builders, the documented path also covers public apps that anyone with the link can open, without Cursor auth — useful for demos and microsites, and the openness that Teams and Enterprise withhold until an admin opts in. The publish click remains the control point: preview first, security review second, live URL only after the user confirms. Cursor’s examples (internal bug trackers, launch microsites with email capture, “deploy this repo as an app”) sit between a throwaway preview and a full DevOps pipeline, and still require a paid plan with cloud agents enabled.
The concrete open question is when GitLab joins Origin and GitHub as a first-class Live Apps source: Cursor only says support for providers such as GitLab is “coming soon,” without a date.
Sources
Related stories
- Cursor Agents Can Now Drive Desktop Apps; Macs Need 2 Permissions
- Cursor’s Agent SDK Turns AI Agents Into Code Projects You Can Test
- Cursor Opens Origin App Marketplace With More Than 20 Partner Apps
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X
