Get started with preconfigured sandbox images. Base images are available for every team and you can start building immediately.Documentation Index
Fetch the complete documentation index at: https://hyperbrowser.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
Available Images
imageName | Best for | Includes |
|---|---|---|
node | General Node.js and TypeScript workloads | Ubuntu 24.04, Node.js, /home/ubuntu working directory |
openclaw | OpenClaw-powered agent and coding workflows | Ubuntu 24.04, Node.js, OpenClaw CLI, git, build tools |
claude-code | Claude Code agent and coding workflows | Ubuntu 24.04, Node.js, Claude Code CLI, git, build tools |
codex | Codex agent and coding workflows | Ubuntu 24.04, Node.js, Codex CLI, git, build tools |
python | Python scripts, agents, and data workloads | Ubuntu 24.04, Python 3, pip, venv |
node-chromium | Browser automation, desktop-style flows, and Playwright Chromium workloads | Node.js, Playwright Chromium, desktop session tooling |
Runtime Defaults
All current base images share a few defaults:- Ubuntu 24.04 as the base OS.
- A default
ubuntusudo user with home directory at/home/ubuntu. - Default working directory set to
/home/ubuntu.
Which Image To Choose
-
Choose
nodewhen you want a minimal JavaScript or TypeScript runtime. -
Choose
openclawwhen you want a Node runtime with the OpenClaw CLI preinstalled. -
Choose
claude-codewhen you want a Node runtime with the Claude Code CLI preinstalled. -
Choose
codexwhen you want a Node runtime with the Codex CLI preinstalled. -
Choose
pythonwhen your workload is Python-first and you wantpipandvenvready out of the box. -
Choose
node-chromiumwhen you need a browser-capable image with Chromium already installed and want the best starting point for browser automation or desktop-style workflows.
Next Steps
- For launch parameters and runtime options, continue to Creating Sandboxes.
- To package your own Docker image into a sandbox image, see Build And Upload A Custom Image.