docker-sandbox

Orchestrate isolated Claude Code sessions in Docker sandboxes with git branch restrictions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/calebeynon/claude-code-setup --skill docker-sandbox-calebeynon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-sandbox
Source: https://github.com/calebeynon/claude-code-setup/tree/main/skills/docker-sandbox
Command: npx skills add https://github.com/calebeynon/claude-code-setup --skill docker-sandbox-calebeynon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Isolate Claude Code tasks in a Docker sandbox to prevent credentials leakage, ensure reproducible environments, and simplify debugging across projects.

Core Features & Use Cases

  • Isolated execution: runs Claude Code inside a Docker Desktop microVM with security constraints.
  • Access control: read-only external data access and built-in data-copy workflow for writable workspaces.
  • Lifecycle and governance: enforces git branch restrictions, automatic environment setup, and guided sandbox management for launching, monitoring, and troubleshooting sessions.

Quick Start

Launch a sandbox for your project by running the provided run.sh command and then connect to the sandbox to begin work.

Frequently Asked Questions about docker-sandbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Claude Code in a Docker sandbox to prevent credential leakage?

You can isolate Claude Code sessions in a Docker sandbox by executing the provided run.sh command, which initializes a secure Docker Desktop microVM. This environment restricts uncontrolled access and prevents credentials from leaking.

How does the Docker sandbox manage git branch restrictions and read-only access?

The Docker sandbox manages git branch restrictions using pre-push git hooks enforced during the session lifecycle. It applies read-only datastore access externally, while a built-in data-copy workflow provisions writable workspaces inside the sandbox.

Do I need Docker Desktop to isolate Claude Code sessions for my local projects?

Yes, isolating Claude Code sessions requires Docker Desktop, as the sandbox operates within a Docker Desktop microVM. This provides the necessary security constraints and reproducible environments for local projects.

What is the best way to set up a reproducible environment for isolated AI coding tasks?

Using a Docker sandbox with automated environment setup provides a reproducible space for isolated AI coding tasks. It orchestrates secure sessions via init.sh and run.sh, ensuring controlled data access and branch safety.

Can I copy external data into the sandbox workspace for Claude Code to modify?

Yes, you can copy external data into the sandbox workspace for Claude Code to modify using the built-in data-copy tooling. The sandbox enforces read-only access to external datastores, requiring data to be copied into the writable workspace for modifications.