Skip to main content

Create, import, and manage projects

Use Home, Projects, and App Details together to manage the full lifecycle of a Builder app.

Create a new project​

The fastest path is the main composer on Home:

  1. Open Home.
  2. Describe the app you want Builder to create.
  3. Submit the prompt.
  4. Builder creates a new app, opens a new chat, and starts generating the first version.

You can also create a project from the Projects page using the create card.

Import a GitHub repository​

Use import when the codebase already exists.

  1. Select Import Repository.
  2. Choose a repository from your connected GitHub account or paste a GitHub URL.
  3. Set the app name that should appear in Builder.
  4. Add custom install or start commands only when the repo needs them.
  5. Open the imported app in chat and continue from there.

Hosted Builder is GitHub-first. Local folder import is intentionally hidden in the hosted workflow.

Work from the Projects page​

The Projects page is the workspace-wide app library.

Use it to:

  • sort by last edited, recently created, or name
  • filter by connection status such as GitHub, Supabase, Vercel, or Neon
  • spot favorites faster
  • resume work from preview-backed project cards

Each card can show a cached preview image so teams can recognize the right app before opening it.

Open App Details​

Open App Details when you need project-level control instead of chat-level iteration.

App Details shows:

  • core metadata such as created time, last updated time, and app ID
  • preview thumbnail status
  • cloud status and cloud region when Builder Cloud is enabled
  • GitHub connection status

From the action menu, you can:

  • rename the app
  • copy the app
  • save the app as a template
  • delete the app

Copy an app​

Builder supports two copy modes:

  • Copy app with history: keeps the Git version history
  • Copy app without history: useful when you want a cleaner reset or the current repo history is not worth carrying forward

Copied apps start as separate Builder projects. Connected GitHub and Supabase state is not carried over automatically.

Save an app as a template​

In hosted Builder, Save as Template is available from App Details.

Use it when the app is good enough to become a reusable starter for your team or the community marketplace.

Continue: Work with templates

GitHub on the project surface​

App Details is also where many teams start the source-control flow:

  • connect the app to GitHub
  • confirm the repo and branch mapping
  • add collaborators for the linked repo

If the app will be deployed later, this is the cleanest moment to establish the GitHub connection.

What is different in hosted Builder​

Hosted Builder hides desktop-only file controls such as local project paths, folder rename actions, and manual filesystem management.

That is expected. In the hosted workflow, the project is treated as a managed Builder app rather than a local folder you maintain directly.

When to use each project surface​

  • Use Home for the fastest new-app start.
  • Use Projects when you need to browse or resume across many apps.
  • Use App Details when you need copy, template, delete, GitHub, or cloud metadata actions.