Cursor said in a 5 November 2026 changelog that its cloud agents can now build a web app, set up a database, configure sign-in, and publish a shareable link. That closes the gap between a laptop demo and a tool colleagues can open.
You start a cloud agent (an agent that runs in Cursor’s cloud, not on your machine) and tell it you want to build an app. Cursor’s Apps documentation says this does not work locally. The agent builds the app, adds a Postgres database if needed, puts private and team apps behind Cursor sign-in, and sets up hosting.
If the app needs to reach your systems, such as a data warehouse, Cursor asks for the secrets it needs and says the agent never sees those values. You then preview the app, pick a unique domain, and publish. Nothing goes live until security checks pass and you explicitly publish.
What you can share
Cursor says its own staff in sales, operations, legal, finance, and engineering are building internal apps. The examples it lists include event registration, desk seating, and sales dashboards. Those are Cursor’s own examples, not independent results.
You can start from scratch on Cursor Origin, Cursor’s own source-control host, or deploy an existing Origin or GitHub repo. GitLab support is coming soon. After publish, you can share the app with specific people, groups, or your whole team, all behind Cursor sign-in.
Individual plans can also share apps publicly. Public sharing is off by default for Teams and Enterprise; a team admin can turn it on. A script cannot open a private or team app unless you send a Cursor API key in an HTTP header named x-cursor-app-token.
This is a different job from an agent that answers one prompt and stops. It also differs from AWS Kiro bots that remember recurring coding chores or Perplexity Teammates that own an ongoing role. Those stay with a standing task. Cursor wants the agent to leave you a hosted app.
What it costs
The changelog says Live Apps is available on paid plans that include cloud agents, not on every paid plan. Cursor’s pricing page lists cloud agents from Premium at $30 a month to Ultra at $200, and Teams from $30 per user per month. Plus costs $8 a month and does not include cloud agents.
Cursor’s cloud agent documentation says you need Premium or higher, Teams, Enterprise, or a legacy paid plan. Cloud agents use your plan’s usage at the selected model’s rate, and Cursor asks for a spend limit when you first use them.
Cursor did not list a separate hosting fee in the docs we read. The Apps page says hosting comes “as is” and “as available.” A published app may be revoked, and Cursor says it is not responsible for your apps or their output.
Where it breaks
Four checks run before every publish, even if you turn the broader security review off. They block secrets in app files and credential files. They leave .env files out of what ships and strip source maps, so visitors cannot read the source.
An AI review also reads the files and can block serious issues. Admins can add review rules but cannot remove the built-in checks. They can see every app and secret, turn Apps off, unpublish any app, and approve a blocked publish except for malicious code, hardcoded secrets, or exposed credentials.
You cannot build these apps with a local agent, and GitLab users have to wait. Plus subscribers are out unless they upgrade. You are also trusting a Cursor-hosted app and database with whatever you put in it.
We did not run this workflow ourselves, so we cannot say how long a typical tool takes.
What to do this week
If you already pay for a plan that includes cloud agents, pick one spreadsheet tool, such as an event signup sheet. Ask a cloud agent to build that app, preview it, and read every security finding. Share it with two teammates behind Cursor sign-in before you connect a production database.
Sources
Get the weekly email
The week's most useful AI news, a tutorial and an interview.
Anna Jakovleva
Anna Jakovleva is the senior editor for AI tools at AI Observer, leading coverage of agents and automation, design and product, and the site's tutorials. She worked in operations and product teams before joining, so she judges tools by setup time, cost and where they break. Her writing is hands-on and practical.
Spotted a mistake? Tell us on the corrections page.
