Cloud sandboxes

The Cloud based sandboxes offer easy to setup environments managed by us. This setup is ideal for individual developers, small teams who want to get started quickly. If you’d like to manage your own sandboxes, please contact [email protected].

Each cloud runner uses 4 core CPU with 4GB memory.

Cloud runners

The cloud based runners are currently available in US and EU regions. Each runner consist of a baseline image that contains git binary and claude code CLI along with a few simple tools to manage the lifecycle of these runners.

All our cloud runners are single tenant and do not share permissions or environment with any other task. These act as background agents running claude code and performing operations as directed by the user, while streaming the output back to the controller.

Lifecycle management

Every time a new task is created, a new runner will be spawned in the cloud. The runner will automatically select one of the environments suitable for this task. Cloning an existing Runbook creates a new task and a new runner environment.

A runner will automatically pause after 30 mins of inactivity. You may also choose to pause the runner manually anytime during the task.

To unpause an existing runner, simply post a message on the chat associated with that Runbook. This will reload the runner from the previous saved state and resume the conversation. All the context is loaded back when resuming the runner.

All paused runners are permanently deleted after 4 months of inactivity.

Environment management

Environments control what tools and permissions are enabled for the runners. These environments can be preset for each repository in the Runbooks settings.

Prebuilt environments

For quick setup, we recommend using one of our prebuilt environments:

• Python - Python 3.13, pip, virtualenv, uv, pytest

• Node.js - Node 18 LTS, npm, yarn

• Go - Go 1.21, go mod

• Java - OpenJDK 17, Maven, Gradle

• Ruby - Ruby 3.2, RubyGems, Bundler

• Rust - Rust stable, Cargo

• PHP - PHP 8.2, Composer

• React/TypeScript - Node.js, TypeScript, React, Vite, ESLint, Prettier

• Vue.js - Node.js, Vue 3, Vite, TypeScript support

• Angular - Node.js, Angular CLI, TypeScript

• Next.js - Node.js, Next.js 14, TypeScript, Tailwind CSS

• MEAN Stack - MongoDB, Express, Angular, Node.js, TypeScript

• MERN Stack - MongoDB, Express, React, Node.js, TypeScript

• Django + React - Python, Django, Node.js, React, PostgreSQL

• Rails + Vue - Ruby on Rails, Node.js, Vue.js, PostgreSQL

• Spring Boot + React - Java, Spring Boot, Node.js, React, Maven

• Go + Next.js - Go, Node.js, Next.js, TypeScript

• FastAPI + React - Python, FastAPI, Node.js, React, TypeScript

Custom templates

Create custom sandbox templates when prebuilt environments don't meet your requirements.

Creating a custom template

Navigate to Runbooks Settings > Custom Templates and click Create Template.

Provide:

• Display name: A descriptive name for your template

• Dockerfile content: Instructions to build your environment

Dockerfile requirements

Custom templates use Dockerfiles with some restrictions:

• ADD and COPY commands are not allowed (no local file access during build)

• Use RUN commands to install dependencies via package managers

Example Dockerfile:

FROM ubuntu:22.04

# Install system dependencies
RUN apt-get update && apt-get install -y \
    git \
    curl \
    build-essential \
    && rm -rf /var/lib/apt/lists/*

# Install Node.js 20
RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \
    && apt-get install -y nodejs

# Install Python 3.11 with uv
RUN apt-get update && apt-get install -y python3.11 python3.11-venv \
    && curl -LsSf https://astral.sh/uv/install.sh | sh

# Install project-specific tools
RUN npm install -g pnpm turbo

Build process

After submitting your Dockerfile:

1. The system validates the Dockerfile syntax

2. A build job starts (typically takes 2-10 minutes)

3. Once complete, the template appears in your sandbox configuration options

Using custom templates

Select your custom template in Runbooks Settings > Sandbox Configuration:

1. Set Sandbox Type to cloud

2. Choose your template from the Sandbox Template dropdown

New Runbook sessions will use your custom template.

Timeout configuration

Cloud sandboxes have a configurable timeout (1-240 minutes). Set this in Runbooks Settings > Sandbox Configuration to control how long inactive sandboxes remain running before auto-pausing.

Secrets management

Secrets are credentials that are stored encrypted and can be injected into the runners for each environment. These secrets can be used for two purposes:

• providing access to MCP configuration

• using as environment variables to perform specific actions within the runners

These secrets can be created by anyone, either for the entire organization or just for personal use. Admins can manage the permissions of organization wide secrets. Secrets cannot be retrieved in clear text once saved.