create-claude-playground

What problem does it solve?

Provides a reproducible, per-project sandbox so developers can run Claude Code autonomously without granting it host-level write access or interfering with other projects; it reduces the risk of accidental repository or system modification while enabling iterative development workflows.

Core Features & Use Cases

• Per-folder containers: Each project folder gets its own container named claude-sandbox-<folderName> so multiple isolated playgrounds can coexist.
• Reuses or generates tooling: Reuses existing Dockerfile and a setup script when present, or generates them from templates; stages files, builds images, and configures a non-root claude user.
• Security-first setup: Locks hooks and settings as root-owned read-only, supports optional bind-mounting or copying of host files, and runs verification checks to ensure the claude user cannot modify protected files.
• Use case: Ideal when you want Claude to work autonomously on a single repository (for code generation, testing, or automation) while preventing it from pushing to protected branches or changing repository hooks.

Quick Start

Run /create-claude-playground <folderName> to create and prepare an isolated Docker container for that project, then follow the printed instructions to authenticate inside the container.