On this page
At 05:41:10 Asia/Shanghai on 2026-11-06—matching the @cursor_ai public post timed 2026-11-05T21:41:10Z—Cursor announced Build Live Apps. The changelog page is dated Nov 5, 2026 and carries the H1 Build Live Apps in Cursor. The pitch is direct: most apps written with an agent never leave localhost; Cursor can now build a live app inside the product and return a link that can be shared. A same-thread follow-up at 05:41:13 Asia/Shanghai (2026-11-05T21:41:13Z) states the capability is available now on all paid plans. DigIntoAI has not built an app with this flow, not published or shared one, and not exercised Postgres, Cursor SSO, the security checks, or API keys—the notes below follow the changelog, the official Apps docs, and the public posts as self-reported.
Related reading: Cursor Cloud Agents: Interactive Canvas, Environments API, Cursor Agent SDK Is Out: Folders, Eval, and Deploy, Cursor Pricing (October 2026), and How Cursor Usage Limits Work on The X Subscription and Legacy Plans (October 2026). The Canvas／Environments／API piece and the Agent SDK piece are separate Cloud Agent surfaces—useful for contrast, not the same hosted-live-app-plus-shareable-link feature shipping here. Pricing and usage-limits sit beside the “paid plans with cloud agents enabled” gate.
What the announcement claims
The changelog says describe what to build, and Cursor handles the rest: build the app, set up a database, configure auth, and deploy. The root @cursor_ai post repeats that framing and attaches an about 24-second official video. That clip is Cursor’s demonstration, not a DigIntoAI hands-on recording.
How it works (cloud agent only)
Official docs are blunt: remember to use a cloud agent; this feature is not supported locally. Kick off a cloud agent and say explicitly that the goal is to build an app. Cursor scaffolds the web app, spins up a Postgres database when needed, sets authentication behind Cursor SSO, and provisions hosting. If the app must reach other systems—such as a data warehouse—Cursor asks for the secrets it needs. The docs add that the agent never sees the secret values; in most team setups an admin creates team secrets in the Apps dashboard.
When publish starts, a unique domain is chosen and Cursor returns a live link. Apps can come from a new or existing repository. Supported git surfaces today are Cursor Origin and GitHub; the changelog says support for other providers such as GitLab is coming soon. Hosting places each app in a dedicated account created for the team (or for the individual-plan account); those hosting accounts are isolated from one another.
Publish, security checks, and admin controls
Publish is not automatic. The docs describe a preview tray, a URL choice (changeable later), then a run of deterministic and agentic security checks. If every check passes, Cursor returns a live link. If a check fails, the agent lists what still needs fixing; fix, then publish again. Nothing goes live until the checks pass and publish is chosen explicitly.
Four hard checks always run before every publish—even when the AI security review is turned off:
- Block secrets written in app files
- Block credential files
- Never publish
.envfiles - Never publish source maps
On top of those, an AI security review reads app files and can block serious issues. Team admins may add custom review instructions; custom rules can add requirements but cannot remove Cursor’s built-in checks. Admins can also see every app and secret on the team, approve publishes the review blocked (except for malicious code, hardcoded secrets, or exposed credentials), unpublish any app, toggle Apps on or off, allow or disallow public apps and API-key access, and review changes in the audit log.
Sharing and who can open an app
After checks pass, the app deploys to the chosen URL. Visibility options in the docs are:
| Visibility | Who can open it |
|---|---|
| People invited | Only the owner or specific signed-in members／groups |
| Team | The whole Cursor team, signed in |
| Public | Anyone with the link |
Private and team apps sit behind Cursor sign-in. On individual plans, apps can also be shared publicly without requiring Cursor auth. Public sharing is disabled by default for Teams and Enterprise; a team admin can turn it on in the Apps dashboard.
For scripts, CI, or Grok Bot, a Cursor API key can open an app the way a signed-in visitor would. The key goes only in the x-cursor-app-token HTTP header—no query parameter and no cookie. Personal keys open apps the owner can open; team keys open only granted team apps; public apps accept either key.
Who gets it
Both the changelog and the docs say Apps／Build Live Apps is available on all paid plans with access to cloud agents (changelog: all paid plans with cloud agents enabled). That gate is not Free and not a local-agent path. Plan names and metering sit next to the pricing and usage-limits notes linked above.
Example uses Cursor lists (not DigIntoAI tests)
The changelog names internal examples—not DigIntoAI evaluations—including ops tools (event registration, account assignments, desk seating), multimedia customer presentations, training／onboarding, live sales pipeline dashboards, and engineering-service portals. The follow-up post echoes live dashboards, customer presentations, internal ops tools, onboarding, and developer portals.
Not the same as Agent SDK or Canvas／Environments／API
Build Live Apps means a hosted web app (dashboard, portal, microsite) plus a shareable link, with security checks before anything goes live. That is not the Agent SDK programming surface, and not the earlier Cloud Agents Canvas／Environments／API feature set. Those DigIntoAI notes remain useful contrast reading; they are not a claim that Origin App Marketplace shipped under this name.
Official disclaimer (one line)
The Apps docs end with a short disclaimer: Cursor provides technology and tools, does not warrant apps or outputs, and treats hosting as separate from its services, provided as is／as available.
DigIntoAI status
We haven't tested scaffolding an app, provisioning Postgres, configuring Cursor SSO, running the security checks, publishing a live link, inviting teammates, turning on public sharing, or calling an app with x-cursor-app-token. The ~24-second root-post video is an official demo, not a DigIntoAI retest. The notes follow the changelog, the official Apps docs, and the @cursor_ai posts only.
In short
Cursor’s Build Live Apps (changelog Nov 5, 2026; @cursor_ai 05:41 Asia/Shanghai on 2026-11-06) lets a cloud agent—not a local agent—scaffold, host, and share a live app link on paid plans with cloud agents enabled. Publish runs deterministic and agentic checks, including four always-on hard gates; nothing goes live until checks pass and publish is chosen. Teams／Enterprise keep public sharing off by default; individual plans can share publicly. We haven't tested the flow; the notes follow official sources only.