devbox create.
Creating a Devbox
Give the Devbox a name, an image, and a size. Anything you leave out falls back to a workspace default.- CLI
- TS SDK
- Dashboard
Run Or pass them inline to skip the prompts:
devbox create with no arguments to be prompted for each value:Create a macOS Devbox
Ask for macOS instead of the default Linux.- CLI
- TS SDK
- Dashboard
--platform also accepts macos/arm64, linux, and linux/amd64.Create from a blueprint
Create a Devbox from a saved Blueprint definition.- CLI
- TS SDK
- Dashboard
--blueprint uses the latest version of the named Blueprint, and cannot be combined with --from or --platform.Create from a spec file
Declare the configuration in a file, then create from it non-interactively:devbox.yaml
Configuration Options
Set these when you create a Devbox, in any of the forms above.Image
Choose the image the Devbox starts from.- CLI
- TS SDK
- Dashboard
--platform linux or --platform macos. To create from a macOS image, pass the platform and the image name together:tahoe or sequoia, and each bundles a macOS and Xcode version. Only Linux Devboxes can use images you build yourself.
To bake your own tools and runtimes into an image, see Custom Images.
Machine Size
Choose how much CPU and memory the Devbox gets.- CLI
- TS SDK
- Dashboard
- Linux
- macOS
Linux vCPU counts represent burstable capacity.
Your workspace policy may restrict which sizes are available.
Repository
Clone a repository into the Devbox when it is created. This requires a connected GitHub organization.- CLI
- TS SDK
- Dashboard
--checkout applies the workspace default repository. Pass --no_checkout to skip the checkout entirely.repository block in a spec file.
Access Mode
Choose whether the Devbox is private to you or shared with the workspace. When omitted, the workspace default applies.- CLI
- TS SDK
- Dashboard
--access_mode accepts private or shared.Idle Timeout
Control how long a Devbox stays running after it goes idle. The dashboard offers presets of 15 minutes, 30 minutes, 1 hour, 4 hours, and 8 hours, plus a custom value. The CLI accepts any duration.- CLI
- Dashboard
Volume Size
Persistent storage defaults to the workspace setting. Override it when a repository or build cache needs more room:- CLI
- TS SDK
- Dashboard
Ephemeral
Create a Devbox whose instance and storage are deleted when it stops.- CLI
- TS SDK
Site
Pin the Devbox to a specific site. By default it is created in the site closest to you.- CLI
- TS SDK
devbox site-latency:Workspace Defaults
Workspace admins can set default values applied to all newly created Devboxes. Navigate to the Defaults page in the dashboard to configure:- Image: default base image, which also determines the operating system (Linux or macOS)
- Instance size: default CPU and memory allocation
- Volume size: default persistent volume size for new Devboxes
- Git repository: default repository to clone
- Access mode: private (just you) or workspace-wide (shared with all members)
- Auto-stop timeout on idle: how long Devboxes stay running when idle
- Egress policy: default outbound network access restrictions
- Bazel: enable Bazel integration to share Bazel cache across Devboxes
- Tailscale: default Tailscale integration spec to connect Devboxes to your tailnet
Pin an exact image
--image follows the latest build of a named image, so a Devbox created today and one created next month can differ. To pin a single build that never changes, pass a full registry reference to --image_ref instead.
List the images with their references:
Output
image_ref value to devbox create:
--image and --image_ref are mutually exclusive. --image_ref applies to Linux images only: macOS Devboxes must use --image with a macOS image name.
GitHub CLI Authentication
Forward your localgh CLI authentication to a Devbox so gh commands and HTTPS git operations are authenticated. Do it at creation time, or against a Devbox that already exists:
- At creation
- Existing Devbox
- Spec file
gh token is read before the Devbox is created, so a missing or expired login fails fast. When both are given, the --setup_github flag overrides the spec value.
Next Steps
Devbox Lifecycle
Listing, starting, stopping, idleness, and deleting.
Sessions
Persistent terminal sessions that survive disconnections.
Blueprints
Reusable Devbox configurations to create from.