coding-sandbox

Proposes and operates confirmed local Docker sandboxes for coding agents.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill coding-sandbox-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-sandbox
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/coding-sandbox
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill coding-sandbox-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running AI coding agents directly on your host machine risks exposing neighboring projects, credentials, and system state. This Skill creates isolated, per-project Docker sandboxes so each agent works only within its intended scope. ## Core Features & Use Cases - Stack Inspection and Proposal: Inspects the project stack and proposes a sandbox with explicit packages, bind mounts, and a confirmation hash before anything is created. - Isolated Per-Project Containers: Creates one Linux sandbox per project and agent combination, supporting claude-code, codex, opencode, pi, and kimi-code, without exposing neighboring projects. - Lifecycle Operations: Provides start, stop, freshness-check, and clean commands for interactive TUI sessions inside the sandbox. - Use Case: You want Claude Code to work on your backend repo without access to your other projects. Ask for a coding sandbox, review the proposed binds and hash, confirm, and open an interactive session in the isolated container. ## Quick Start Ask the agent to set up a coding sandbox for this project and confirm the proposed configuration hash before it builds the container.

Frequently Asked Questions about coding-sandbox

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

FAQPage Schema
How do I create an isolated Docker sandbox for a coding agent?▼

Run the proposal command with the project and agent name, review the stack, packages, binds, and confirmation hash, then repeat the command with the hash to confirm. The sandbox is created only after explicit confirmation of that exact proposal.

Which coding agents are supported in the Docker sandbox?▼

The sandbox supports five agents: claude-code, codex, opencode, pi, and kimi-code. Any other agent requires stopping for a decision rather than proceeding with an unsupported configuration.

What host requirements does the coding sandbox need?▼

The host must run Arch Linux or a Debian-based Linux with Docker installed. Expected bind sources include git credentials, gitconfig, git config directory, gh config, and the selected agent's state directory.

Can the sandbox access Docker on the host machine?▼

No, the sandbox never mounts the host Docker socket and never runs privileged. If a project needs Docker, the client, daemon, images, volumes, and networks all stay inside the sandbox.

How do I stop or remove a coding sandbox container?▼

Use the generated stop.sh script to halt processes while preserving the environment, or clean.sh to remove the container, image, and internal resources after its confirmation. Then run the rm command to delete generated artifacts.