Runtime Catalog
A DevBox is the machine an agent works in — a full container (or Windows VM) with a coding agent, a real shell, your languages, and an optional graphical desktop. This page is the canonical reference for what’s in a DevBox and what you can add.
AI runtimes
Section titled “AI runtimes”Every DevBox ships with an AI coding agent. ClusterCode supports three engines today — Claude Code, Codex, and GitHub Copilot — with more coming.
Languages
Section titled “Languages”Add the languages you work in to a DevBox — Python, Go, .NET, Rust, Java, Ruby, PHP, and more — so the agent has the toolchain it needs without writing a Dockerfile. Select them when you configure the image; they’re installed into the DevBox and ready to use.
Terminal tools
Section titled “Terminal tools”Every DevBox comes with a real, comfortable shell out of the box:
- GitHub CLI (
gh) - Neovim (with NvChad)
- Oh My Posh (shell prompt)
- Nerd Font (terminal icons)
- Shell config — sane history, readline, and tab completion
Infrastructure dependencies are always present:
- Git, Node.js, tmux, curl
You can open the live terminal on any DevBox and drive it yourself — start an agent, watch one work, jump in mid-task, or pair with it line by line.
Visual desktop
Section titled “Visual desktop”DevBoxes can include a real graphical desktop, with VS Code and a Chromium that already has the Claude extension wired in. With the Display capability on, an agent can open your running app, see the rendered UI, and click through it.
See Visual testing for the full capability, and note it works on Windows DevBoxes too.
Authentication
Section titled “Authentication”Each agent authenticates with its own credentials:
| Agent | Required credential |
|---|---|
| Claude Code | Anthropic API key, Claude OAuth token, or platform credits |
| GitHub Copilot | COPILOT_GITHUB_TOKEN + GH_TOKEN |
| Codex | OPENAI_API_KEY |
Credentials are configured in the orchestrator. See Environment Variables.
Bring your own image (BYOI)
Section titled “Bring your own image (BYOI)”On Pro and Enterprise plans, you can build your own DevBox images to:
- Add project-specific dependencies
- Pre-install language runtimes
- Include proprietary tools
- Configure a custom shell environment
See Custom Containerfile. You can also snapshot a configured DevBox into a reusable golden image so future launches start from exactly the state you set up.
Capability matrix
Section titled “Capability matrix”For the full per-agent capability matrix, see Supported Agents.
Related
Section titled “Related”- Engines — the engine table (not duplicated here)
- Visual testing
- Windows Containers
- Cloud workers — where a DevBox can run
- Build an Image from a Container