Buildspace
CLI

App Management

Create, list, delete, and manage hosting for your Buildspace apps.

List Apps

buildspace app list

Shows all your apps with the active app marked.

buildspace app list --json

Returns JSON with apps and activeApp fields.

Show Current App

buildspace app current

Displays the currently resolved app and how it was determined (flag, git remote, or active selection).

Set Active App

buildspace app use <slug>

Sets the default app for commands when no --app flag is provided and you're not inside a Buildspace git repo.

Create an App

buildspace app create --name "My App"

Options

FlagDescription
--name <name>App display name (required)
--slug <slug>Optional slug override
--description <text>Optional description
--category <value>Optional category
--jsonOutput result as JSON

If you omit --slug, Buildspace generates one from the app name. When a generated slug is already taken, Buildspace retries with a similar slug plus a short four-character suffix.

The new app is automatically set as the active app. Initial API keys are displayed after creation.

Typical next step:

buildspace init --app <generated-slug>
cd <generated-slug>
bun install

Delete an App

buildspace app delete <slug> --confirm <slug>

Performs a soft delete. The --confirm flag must match the slug exactly. Optionally add --note <text> to record why the app was deleted.

Hosting

Manage per-environment hosting for your app.

Check Status

buildspace app hosting status
buildspace app hosting status --env prod
buildspace app hosting status --json

Enable Hosting

buildspace app hosting enable --env dev

Disable Hosting

buildspace app hosting disable --env prod

All hosting subcommands accept --app <slug> and --env dev|prod (defaults to dev).

If you are already inside a cloned Buildspace app repo, you usually do not need --app because the CLI resolves the app from the git remote.

On this page