Cursor Cloud Agents Can Now Start Apps From Scratch

Cursor Cloud Agents can now start a web app from scratch without a connected repository. Cursor says the workflow can create an Origin repository, show a live preview, and publish the result through Vercel. (Cursor on X; Cursor changelog)

From prompt to project

Previously, a Cloud Agent workflow commonly began with an existing codebase. The new start-from-scratch flow removes that first dependency: describe the web app, let Cursor create the project, and use the resulting Origin repository as the place where the work is stored. (Cursor on X; Cursor changelog)

Cursor's follow-up says the flow can use a private or internal repository, which makes it more useful for prototypes that are not ready to publish publicly. The repository gives the agent a durable project boundary instead of treating the first generation as a disposable chat response. (Cursor on X)

The workflow

The start-from-scratch path is built around four steps:

1. Describe the app: Give Cloud Agent a prompt for the site or web app you want to create.
2. Create the project: Cursor creates an Origin repository for the new code.
3. Preview it: Review the generated app in a live preview before sharing it.
4. Publish with Vercel: Use the Vercel integration to deploy the result.

The important change is the handoff between creation and deployment. A user does not need to create a repository locally, configure a first branch, or assemble a preview pipeline before seeing whether the idea works. (Cursor changelog)

Where it fits with Origin

Origin is Cursor's hosted code platform, with repository storage and agent workflows in the same product. The start-from-scratch update builds on that foundation, but it is a different use case from syncing an existing GitHub codebase: the project begins inside Cursor and can stay private or internal while it takes shape. (Cursor changelog; Cursor Origin changelog)

That makes the feature useful for quick prototypes, internal tools, landing pages, and early product experiments. It is not a guarantee that generated code is production-ready; the live preview is a checkpoint for testing the result before deciding whether to publish it.

A safer way to try it

1. Start with a small app whose requirements are easy to review.
2. Ask the agent to explain the generated routes, data flow, and external services.
3. Inspect the preview and test the main user paths.
4. Keep the Origin repository private or internal until the code and dependencies are reviewed.
5. Publish to Vercel only after checking secrets, forms, auth, and any data-handling behavior.

The value is speed between an idea and a working preview. The repository and deployment steps still need normal engineering review, particularly when a prototype handles user data or connects to external services.

Sources

• Cursor on X, “Cloud Agents can now start from scratch,” August 27, 2026: https://x.com/cursor_ai/status/2093077548649570777
• Cursor on X, follow-up on private and internal repositories, August 27, 2026: https://x.com/cursor_ai/status/2093077549786300747
• Cursor, “Start from scratch”: https://cursor.com/changelog/start-from-scratch
• Cursor, “Origin code hosting”: https://cursor.com/changelog/origin-code-hosting