sandbox-exec

Execute high-risk shell commands inside isolated uv venv or Docker environments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill sandbox-exec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sandbox-exec
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/sandbox-exec
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill sandbox-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute high-risk shell operations inside a protected, isolated environment to prevent local machine contamination and accidental damage.

Core Features & Use Cases

  • Isolated execution with uv venv by default, providing process isolation and minimal dependencies.
  • Docker-based OS-level isolation as a fallback for heavier tasks requiring container boundaries.
  • Safe, auditable workflow for dependency upgrades, database migrations, scaffold generation, and destructive file operations.

Quick Start

Set SANDBOX_MODE in SCRATCHPAD.md and run sandbox-exec:run <command> to execute it inside an isolated environment.

Frequently Asked Questions about sandbox-exec

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

FAQPage Schema
How do I isolate risky shell operations like database migrations to protect my local machine?

To isolate risky shell operations, execute them inside a protected environment using uv venv by default or Docker for heavier tasks. This prevents local machine contamination during database migrations, dependency upgrades, and destructive file operations while capturing logs and automating teardown.

What is the best way to sandbox dependency upgrades and scaffold generators?

The best way to sandbox dependency upgrades and scaffold generators is executing them inside isolated environments. Using uv venv provides process isolation with minimal dependencies, while Docker offers OS-level isolation as a fallback for commands requiring stricter container boundaries.

Can I use Docker for shell command isolation instead of uv venv?

Yes, you can use Docker for shell command isolation instead of uv venv. Docker acts as a fallback providing OS-level container boundaries for heavier tasks, while uv venv remains the default for standard process isolation with minimal dependencies during destructive file operations.

How do I configure sandbox mode for executing destructive file operations?

To configure sandbox mode for destructive file operations, set the SANDBOX_MODE variable in SCRATCHPAD.md. This mode selection controls how commands execute within the isolated environment, ensuring safe auditable workflows with log capture and teardown orchestrated via sandbox IDs.

When should I not use uv venv for isolating shell commands?

You should not use uv venv for isolating shell commands when tasks require heavier OS-level isolation or container boundaries. In these cases, switch to Docker as a fallback to safely execute high-risk shell operations and prevent accidental damage during destructive file operations.