Cursor app building is good for quickly building small internal tools and sharing them with colleagues: this feature, launched on November 5, is handled by a cloud agent, and building the app, setting up the database, adding sign-in, and publishing all happen inside Cursor. It is not meant for products sold directly to outside customers. First confirm you are on a paid plan, then start.
- Update Cursor to the latest version, open a cloud agent, and describe in one sentence what you want, for example: "Build an internal app where my team can submit bug reports and track their status."
- The cloud agent scaffolds a first version of the app; when data needs storing, it automatically provisions a Postgres database, and sign-in goes through Cursor single sign-on, so you do not have to wire up your own account system.
- Click through the core flow in the preview to confirm that submitting, viewing, and changing status all work; if something is off, ask the agent in the chat to fix it.
- Pick a web address, pass the security checks, and click publish. You get a shareable link to send colleagues; they sign in with their Cursor account and can use the app.
- You can keep changing it after publishing and publish again; the old link stays the same.
Three limits to be clear about first
First, this feature is only available on cloud agents; local agents cannot use it, and the free plan does not include it. Second, code repositories can only live on Cursor Origin or GitHub; GitLab support is still on the way, so teams on GitLab should not rush to migrate. Third, an app must pass security checks before it goes live; if it fails, it cannot be published. For sensitive data or publicly accessible scenarios, assess the compliance requirements first, and the vendor has not published a separate hosting price or usage cap.
Sharing comes in three levels: specific people only, your whole team, or a public link. Team and Enterprise plans have public sharing off by default, and an admin has to turn it on; on individual plans you can share publicly and viewers don't need to sign in to Cursor. Before every publish, four checks always run: no secrets in app files, no credential files, no .env files, and no source maps — if anything is found, the app can't go live.
It fits internal tools best: bug tracking, event registration, desk seating, onboarding checklists, and data dashboards — needs that are clearly defined and whose users are your own colleagues. For outward-facing products, complex permission levels, or high concurrent load, do not expect it to do everything in one step. Try it first with one real small need; once the flow works, decide whether to move more internal tools over.
