Verdict, November 6, 2026. Docs-only. OP if you already have a paid Cursor plan with cloud agents, and you need an internal dashboard, portal, microsite, or ops tool shared with named people, groups, or your team behind Cursor sign-in. Tell the cloud agent to build an app. Publish only after the checks pass and you choose to publish. Mid as the host for a public customer product that needs your own auth and your own infra. Mid on Free or Plus, which do not include cloud agents. Mid when the repo you need to ship is GitLab only: the November 5 changelog says that support is coming soon. Cursor stays A on the October 15 AI Coding Agents list. No letter moves. S is empty until a hands-on test is documented. OP or Mid has not built or published one of these apps.
Pages below were read November 6, 2026. The changelog entry is dated November 5, 2026. Behavior that entry describes is a vendor claim.
Say "build an app" to a cloud agent
NEW On November 5, 2026, Cursor announced live apps. Kick off a cloud agent and tell it you want to build an app. The docs say this is not supported locally. From scratch, Cursor creates a repository on Cursor Origin. You can also deploy an existing GitHub repository. Cursor scaffolds the web app, can provision Postgres, sets auth behind Cursor SSO for private and team apps, and provisions hosting. A tray shows a preview. You then pick a unique domain or URL, which you can change later. Nothing goes live until the checks pass and you explicitly publish. One documented prompt is "Build an internal app where my team can submit bug reports and track their status." That line is the docs' sample. OP or Mid did not run it. Sources: changelog, November 5, 2026 (opens in a new tab), apps docs (opens in a new tab).
VENDOR CLAIM The changelog's own examples are internal tools, with no count and no uptime figure. If the app must reach your systems, such as a data warehouse, Cursor asks for secrets. The agent never sees the values. In most cases a team admin creates team secrets in the Apps dashboard. Personal secrets require an account that can create them. Sources: changelog, November 5, 2026 (opens in a new tab), apps docs (opens in a new tab).
Who the link is for
BUFF Sharing is invite-only, team, or public. Invite-only is you, or specific team members and groups, signed in to Cursor. Team is your whole Cursor team, signed in. Public is anyone with the link, and it does not require Cursor auth. Behind Cursor sign-in is the OP case. Source: apps docs (opens in a new tab).
NERF Public sharing is off by default for Teams and Enterprise. A team admin turns it on in the Apps dashboard. Turning it off moves existing public apps back to team visibility. The changelog says individual plans can share apps publicly. That switch is not a customer-product host. A Cursor API key lets a script or Grok Bot through sign-in. Personal keys open apps their owner can open. Team keys open only the team apps they were given. Send x-cursor-app-token on every request. There is no query parameter and no cookie. A refused key gets the sign-in redirect, and the call is marked automated under the key, not a person. Admins can disallow those keys. Sources: apps docs (opens in a new tab), changelog, November 5, 2026 (opens in a new tab).
Four checks, then an admin
BUFF Four checks run before every publish, including when the extra security review is off. They block an API key or access token written in an app file, private keys, service-account keys, and files with auth tokens. They leave .env files out of what ships, and they remove source maps. An AI security review reads the files on top of those four and can block until you tell the agent to fix the list and publish again. Team admins can add review instructions. Added rules cannot remove the four checks. Admins can see every app and secret, turn Apps on or off, approve a publish the review blocked, and unpublish any app. Approval does not cover malicious code, hardcoded secrets, or exposed credentials. Setting changes go to the team's audit log. Sources: apps docs (opens in a new tab), changelog, November 5, 2026 (opens in a new tab).
Where this is not your host
NERF The November 5 changelog limits app deploys to new or existing repos on Cursor Origin and GitHub. Other git providers, with GitLab named, are coming soon. Cloud agents in general can already connect to GitHub, GitLab (Cloud and Self-Hosted), Bitbucket Cloud, or Azure DevOps. That is the clone path, not the app-publish list. An existing GitLab repo is Mid for this deploy. A new internal tool can still start on Cursor Origin. Before a cloud agent starts from a repository, a Cursor account admin has to connect source control. Start from scratch is the no-repository path, and it is how a new app gets an Origin repo. Sources: changelog, November 5, 2026 (opens in a new tab), cloud agents (opens in a new tab), apps docs (opens in a new tab).
NERF Each app is hosted in a dedicated account Cursor creates for your team, or for you on an individual plan, isolated from other teams and users. The apps page says Cursor only provides technology and tools, does not provide any "reps or warranties," and is not responsible for your apps, including prompts and outputs. Publication is not an endorsement. A subdomain, account, or published app may be revoked. Hosting is separate from Cursor's services and is provided "as is" and "as available." That is the Mid for a production product with your own auth and your own infra. Source: apps docs (opens in a new tab).
Free and Plus do not have the button
NERF The apps page and the November 5 changelog both limit this to paid plans that have cloud agents. The cloud agents page names those plans: Premium and higher, Teams, Enterprise, or a legacy paid plan. Free and Plus do not include them. Cloud agents bill like other agent work, at the selected model's rate. A larger context window can raise token use. The first run asks for a spend limit. On legacy request-based plans, the page prices them at API rates plus the Max Mode upcharge against included requests. The apps docs print no separate deploy price, and this article does not add one. The changelog index, read the same day, still leads with the November 5 entry. Sources: apps docs (opens in a new tab), changelog, November 5, 2026 (opens in a new tab), cloud agents (opens in a new tab), changelog index (opens in a new tab).
The board stays put
No letter moves. Cursor stays in A on the October 15 AI Coding Agents list. S is empty until a hands-on test is documented. Live apps are a publish path on that rank, read from docs, not a hands-on retest. The Cursor row is unchanged.
What to do today
- Already on cloud agents: try one internal tool. Tell a cloud agent, not a local one, to build an app. Leave public share off until you know who should see it. Publish only after the checks pass and you choose to publish.
- On Teams or Enterprise, confirm an admin can see the app and its secrets before a real credential goes into the Apps dashboard.
- On Free or Plus, skip until the plan includes cloud agents. If the app must ship from an existing GitLab repo, wait. A new internal tool can start on Cursor Origin.
Saturday's email is the coding-agent decision for the plan you already pay for: one OP or Mid call, what got buffed or nerfed, and one fix you can run. The weekly patch is on beehiiv: subscribe free (opens in a new tab).
The OP or Mid Team
Sources
Checked November 6, 2026.
- Cursor changelog: Build Live Apps in Cursor, November 5, 2026 (opens in a new tab)
- Cursor docs: Cloud Agent Apps, read November 6, 2026 (opens in a new tab)
- Cursor docs: Cloud Agents, plan list including Free and Plus, read November 6, 2026 (opens in a new tab)
- Cursor changelog index, read November 6, 2026 (opens in a new tab)