Getting Started
Enable GitHub integration
Enable the GitHub integration by visiting Devboxes, clicking Connect Organization, and following the instructions.
Authenticate with Namespace
Authenticate with Namespace using the Devbox CLI:This opens your browser to complete authentication. Once logged in, you’re ready to create and manage Devboxes.
Create a Devbox
Create a Devbox with the default base image.If
- CLI
- Dashboard
--checkout is provided, the repository will be cloned into the Devbox.Lifecycle
Namespace manages your Devbox lifecycle automatically:- Start on-demand: Devboxes start when you connect or trigger them
- Pause when idle: After a period of inactivity, Devboxes automatically pause to save costs
- Persistence: Your code, files, and configuration remain intact across pause/resume cycles
- Fast resume: Paused Devboxes resume in seconds
Use Cases
Shared Environment Definitions
A key advantage of Devboxes is that developers and AI coding agents share the same environment definition. This ensures:- Consistent behavior: Code that works in Claude Code will work for developers, and vice versa
- Reproducible results: Everyone sees the same build outputs, test results, and runtime behavior
- Single source of truth: One Dockerfile defines the environment for your entire team, including AI agents
- No environment drift: Eliminate “works on my machine” problems between humans and AI
Developers
Devboxes provide consistent, high-performance environments for development teams:- Onboard new team members instantly
- Work in the same environment as Claude Code and other AI agents
- Access powerful compute for resource-intensive workloads
- Switch between projects without managing local dependencies
- Built-in git access for seamless source control operations
AI Coding Agents & Claude Code Workspaces
Devboxes are optimized for AI-powered development workflows. Claude Code can be enabled directly at instance creation, with the workspace configured automatically:- One-click enablement: Enable Claude Code when you create an instance for automatic workspace configuration
- Quick workspace creation: Spin up isolated Devboxes for each major change or feature
- Shared environment definition: AI agents use the same Dockerfile and tools as your developers
- Parallel development: Work on multiple features simultaneously, each in its own Devbox
- Clean slate: Start fresh for each task without polluting your main environment
- Isolated, sandboxed environments: Complete isolation for secure code execution
- Long-running sessions: Support persistent state across agent sessions
- Built-in git access: Full git access for commits, branches, and pull requests
- Automatic resource management: Resources scale based on agent activity
Builds on Namespace’s infrastructure
Devboxes leverage Namespace’s infrastructure capabilities out of the box:- Geographic optimization: Automatically created in a location closer to you to minimize latency
- Cache volumes: Automatically used for fast incremental building and testing, with sub-second lookups and high IOPS
- Persistent volumes: Backed by our high-performance storage for reliable, fast access to your development files
- High-performance Docker builds: Pre-configured remote builders for optimal container build performance
- Remote registry: Built-in access to nscr.io for fast image pulls and pushes
- Build tool caching: Bazel and Turborepo caching pre-configured for maximum build acceleration
- Network performance: Optimized networking for fast git operations and package downloads
- Compute isolation: Each Devbox runs on dedicated resources with guaranteed performance
Platform Support
Devboxes run Linux AMD64 on high-performance hardware. The Devbox CLI and VS Code extension are supported on macOS, Linux, and Windows. You can manage and connect to your Devboxes from any of these operating systems.Next Steps
Managing Devboxes → Machine sizes, lifecycle operations, workspace defaults, and monitoring. Remote Development → Connect to your Devbox via SSH, VS Code, Cursor, Zed, or JetBrains. Sessions → Persistent terminal sessions that survive disconnections. Executing Commands → Run commands in a Devbox withdevbox exec and read their output with devbox logs.
Custom Images →
Build custom base images with your tools and runtimes pre-installed.