Live Apps
A feature introduced by Cursor that allows users to describe requirements in natural language and use a Cloud Agent to automatically build and deploy web applications, with integrated database configuration and security checks.
Timeline (last 90 days)
Only paid plans that include cloud agents can use Live Apps; users who only use local agents cannot get this feature.
Live Apps deployment is secure-by-default: an app does not go live until checks pass and the user actively clicks publish.
Live Apps runs security checks before publishing, focusing on blocking secrets in app files, credential files, dotenv files, and source maps.
Team administrators can view every app in the team, add review rules, approve blocked publishes, or directly unpublish apps.
Live Apps sharing scope can be set to specific people, groups, or the whole team, with access going through Cursor login; individual plan users can choose public sharing.
The video's author suggests first picking an internal team tool (such as a seating chart or a simple information-collection form) to try Live Apps, and publishing it only to colleagues.
The video's author suggests actively trying to break through login authentication after publishing to test permission boundaries, and unpublishing immediately if anything abnormal is found; the author also believes the feature has not yet been fully tested and the first app should be treated as a drill rather than a production delivery.
All Facts (7)
Only paid plans that include cloud agents can use Live Apps; users who only use local agents cannot get this feature.
50%UnverifiedLive Apps deployment is secure-by-default: an app does not go live until checks pass and the user actively clicks publish.
50%UnverifiedLive Apps runs security checks before publishing, focusing on blocking secrets in app files, credential files, dotenv files, and source maps.
50%UnverifiedTeam administrators can view every app in the team, add review rules, approve blocked publishes, or directly unpublish apps.
50%UnverifiedLive Apps sharing scope can be set to specific people, groups, or the whole team, with access going through Cursor login; individual plan users can choose public sharing.
50%UnverifiedThe video's author suggests first picking an internal team tool (such as a seating chart or a simple information-collection form) to try Live Apps, and publishing it only to colleagues.
50%UnverifiedThe video's author suggests actively trying to break through login authentication after publishing to test permission boundaries, and unpublishing immediately if anything abnormal is found; the author also believes the feature has not yet been fully tested and the first app should be treated as a drill rather than a production delivery.
50%