dev-server-sandbox

Run isolated Unix dev-server instances with unique UNIX_ROOTs and dynamic ports.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/onchainengineer/copilot-tree --skill dev-server-sandbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-server-sandbox
Source: https://github.com/onchainengineer/copilot-tree/tree/main/.unix/skills/dev-server-sandbox
Command: npx skills add https://github.com/onchainengineer/copilot-tree --skill dev-server-sandbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables running several isolated unix dev-server instances by creating unique UNIX_ROOTs to avoid lock contention.

Core Features & Use Cases

  • Isolated sandbox environments for each dev-server instance across multiple worktrees
  • Automatic UNIX_ROOT creation and optional cleanup for debugging
  • Dynamic port assignment with BACKEND_PORT and VITE_PORT to prevent conflicts
  • Config and file mirroring from seed roots to reproduce production-like setups
  • Flexible invocation with environment overrides to tailor the sandbox per run

Quick Start

SEED_UNIX_ROOT=~/.unix-dev make dev-server-sandbox KEEP_SANDBOX=1 SEED_UNIX_ROOT=~/.unix-dev make dev-server-sandbox BACKEND_PORT=3001 VITE_PORT=5174 make dev-server-sandbox

Frequently Asked Questions about dev-server-sandbox

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

FAQPage Schema
How do I run multiple isolated dev-server instances without lock contention?

Creating unique UNIX_ROOT directories isolates multiple unix dev-server instances, preventing lock contention across parallel git worktrees. This sandbox approach avoids conflicts when running several instances concurrently.

How do I automatically assign free ports to parallel dev-servers?

Automatically assign free ports to parallel dev-servers by using environment overrides for BACKEND_PORT and VITE_PORT. The sandbox dynamically allocates these to prevent network conflicts during simultaneous execution.

Can I mirror production configurations when setting up a sandbox dev-server?

Yes, you can mirror production configurations by seeding from an existing UNIX_ROOT. Set the SEED_UNIX_ROOT environment variable to copy sandbox files and configs, reproducing a production-like setup in the isolated environment.

How do I keep the sandbox environment for debugging after the dev-server stops?

To keep the sandbox environment for debugging after the dev-server stops, run the make command with the KEEP_SANDBOX environment variable set to 1. This prevents automatic cleanup of the temporary UNIX_ROOT.

Does this sandbox approach work with git worktrees for parallel development?

Yes, this sandbox approach supports parallel usage across different git worktrees. It creates isolated UNIX_ROOTs for each worktree, allowing multiple dev-server instances to run simultaneously without lock or port conflicts.