Clone an App

Clone by Slug

buildspace init --app <generated-slug>

This clones the Buildspace-managed git repository for the app slug into ./<generated-slug>. Use the slug returned by buildspace app create.

Choose a Destination Directory

buildspace init --app <generated-slug> --dir ./apps/<generated-slug>

What buildspace init Does

• resolves your stored CLI auth
• clones the app repository over the Buildspace git gateway
• writes pullable development variables to .env.local when available

Typical Next Steps

cd <generated-slug>
bun install
bun dev

Once you are inside the cloned repository, app-scoped commands such as buildspace deploy, buildspace env, and buildspace app hosting status can resolve the app from the git remote automatically.

AI agent context

After cloning, give your agent full Buildspace context with one command:

npx skills add BuildSpaceStudio/skills

This installs Buildspace skills for Claude Code, Codex, or any AI coding agent. Run it once per project. For the complete SDK and API reference in a single file, see https://docs.buildspace.studio/llms.txt.

Requirements

• a configured CLI token via buildspace auth login, buildspace auth set, or BUILDSPACE_TOKEN env var
• an existing app slug from your Buildspace account, usually returned when you created the app

Common Errors

Missing auth

If no token is configured, run:

buildspace auth login

Git hosting or template setup issues

If cloning fails immediately, the runtime git gateway or starter template configuration may not be fully set up yet. The CLI prints targeted diagnostics for common misconfigurations.