Telemetry

The BuildSpace CLI collects anonymous usage telemetry to help improve the product. Telemetry is enabled by default and can be disabled at any time.

Commands

Check Status

buildspace telemetry status

Shows whether telemetry is enabled and displays the anonymous installation ID.

Enable

buildspace telemetry enable

Disable

buildspace telemetry disable

Environment Variable

Disable telemetry globally by setting the BUILDSPACE_TELEMETRY environment variable:

export BUILDSPACE_TELEMETRY=0

Accepted values to disable: 0, false, off.

What Is Collected

The CLI tracks anonymous product usage events such as:

• Commands run (e.g. deploy, env set, init)
• Command success/failure status and latency bucket
• Auth method used (browser login vs PAT)
• Platform (macOS, Linux, Windows) and runtime (Node, Bun)
• CLI version

What Is NOT Collected

• No source code, file contents, or environment variable values
• No IP addresses or personally identifiable information
• No third-party tracking or advertising

How It Works

• Events are batched in memory during a CLI session
• A single HTTP request is sent at process exit with a 3-second timeout
• If the request fails, events are silently discarded — telemetry never blocks or delays CLI actions
• An anonymous installation ID is generated locally on first use and stored in your CLI config file

Config Location

Telemetry preferences are stored alongside other CLI settings at ~/.config/buildspace/config.json under the telemetry key.