Skip to content

Coding agents

Cursor hosts and deploys apps its cloud agents build

3 min read

Written by an AI model from the linked sources and checked against them by a second model. How we work

All about: Coding agents →
Image: thenewstack.io

Cursor’s cloud agents can now take an app from a prompt to a live link on a domain you pick. They scaffold the web app, spin up a Postgres database if it needs one, put sign-in behind Cursor SSO and provision the hosting, the company announced on November 5 in a Cursor changelog post. It works only from cloud agents, on paid plans that have cloud agents enabled, and The News Stack points out that agents running locally can’t use it.

To try it, update Cursor, start a cloud agent and tell it explicitly that you want to build an app. If the app has to reach your own systems, a data warehouse for example, the agent asks for the secrets it needs. The News Stack adds that you can preview the result before you publish.

Cloud agents already ran in isolated cloud VMs with full development environments: cloned repos, installed dependencies, secrets, network access. So the new part appears to be the last stretch: the database, auth, hosting and a review gate. The News Stack’s headline casts it as Cursor going after Lovable and Replit.

Which repos can deploy

A new app gets a fresh repository on Cursor Origin, the Git hosting service Cursor launched in August as an agent-centric alternative to GitHub, The News Stack reports. Existing repos can be deployed from Origin or GitHub, so a project already on GitHub doesn’t have to move to Origin first. Cursor says support for other git providers, GitLab among them, is “coming soon.”

Cloud agents themselves already clone from GitHub, GitLab, Azure DevOps Services or Bitbucket Cloud, per Cursor’s documentation. Deployment starts with only Origin and GitHub.

Who decides what goes live

When you publish, Cursor runs deterministic and agentic security checks for common problems. The examples it gives are secrets written into app files and exposed credentials. If a check fails, the agent tells you what it needs to fix, and nothing goes live until the checks pass and you explicitly publish.

Team admins see every app and every secret on the team. They can add their own rules to the security review, approve a publish the review blocked, and unpublish any app. Once the checks pass, the app deploys to the URL you chose.

Sharing goes to specific people, groups or the whole team, all behind Cursor sign-in. On individual plans, apps can also be shared publicly.

What people build with it

Cursor says people in its sales, operations, legal, finance and engineering teams are building internal apps this way. The examples include ops tools for event registration, account assignments and desk seating, live pipeline dashboards for sales, onboarding material for new hires, customer presentations that mix slides, video and interactive demos, and portals for managing engineering services.

An app doesn’t have to be opened by a person, either. You can provision a Cursor API key so that a script or Grok Bot can use it. Grok Bot is a computer-use agent that runs tasks on cloud computers, and Cursor itself now belongs to SpaceX, which bought it for $60 billion in August, according to The News Stack.

No comments yet. Be the first.

Join the conversation

Sign in to leave a comment. It appears after moderation.