Skip to main content
microsandbox exposes one CLI and SDK surface across the local runtime and microsandbox cloud. Local is the default; cloud requires explicit intent and a usable credential. Use the simplest selector that matches who owns the decision:

Environment

The MSB_BACKEND environment variable forces a backend for a single command or shell:
Cloud selection and credentials are separate. MSB_API_KEY does not select cloud by itself. MSB_API_URL only overrides the cloud endpoint and does not select cloud either.

SDK selection

Programmatic selection wins over environment and profile resolution. Use it when the application should decide regardless of where it is launched:

Profiles

Profiles are named backend configurations in ~/.microsandbox/config.json. Use them when you switch regularly or want a shared default for an environment:
active_profile sets the default. MSB_PROFILE=<name> selects another profile for one command:
Cloud profiles require api_key_ref. The optional url field defaults to https://api.microsandbox.dev; set it only for a development, self-hosted, or on-premises control plane. See the profiles schema for every field and credential-reference format.

Resolution order

Backend resolution uses this order:
  1. Programmatic backend set by the SDK
  2. MSB_BACKEND=local|cloud
  3. MSB_PROFILE=<name>
  4. active_profile
  5. Local runtime
Selecting a cloud profile with MSB_PROFILE or active_profile is explicit cloud intent when that profile has "backend": "cloud". MSB_BACKEND=cloud without a usable API key or cloud profile returns a configuration error; it never falls back to local execution.

Inspect the resolved backend

Use msb context to inspect the backend kind, selection source, profile, and cloud API URL without exposing the API key:
The SDKs expose the same secret-safe information:
For global defaults and profile storage, see Configuration. For backend feature differences, see Cloud compatibility.