skills.rest
coder
coderOFFICIAL
Explore all skills by this author →
Website𝕏@coderhqGitHub

dev-server-sandbox

Launch isolated Mux dev-server instances with temporary MUX_ROOT directories.

2.0k|126|Updated Sep 17, 2025
Search Tags:#automation#worktree#parallel#sandbox#ports#dev-server#mux
One-click install
npx skills add https://github.com/coder/mux --skill dev-server-sandbox-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-server-sandbox
Source: https://github.com/coder/mux/tree/main/.mux/skills/dev-server-sandbox
Command: npx skills add https://github.com/coder/mux --skill dev-server-sandbox-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables running multiple isolated mux dev-server instances by provisioning each with its own temporary MUX_ROOT, preventing cross-instance lockfile conflicts and port collisions.

Core Features & Use Cases

  • Create independent sandbox MUX_ROOTs for parallel dev-server experiments across different worktrees or projects.
  • Automatically allocate free BACKEND_PORT and VITE_PORT and expose them to the sandbox environment.
  • Seamlessly reuse provider configs and project lists while keeping each instance isolated for debugging and testing.

Quick Start

Run make dev-server-sandbox to spin up a sandboxed MUX_ROOT and start a new dev-server instance.

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 parallel dev-server instances without port collisions?▼

You can run isolated mux dev-server instances by provisioning each with a temporary MUX_ROOT, which automatically allocates free BACKEND_PORT and VITE_PORT to prevent cross-instance lockfile conflicts and port collisions.

How do I test across multiple git worktrees using a dev-server sandbox?▼

Testing across git worktrees involves spinning up isolated mux dev-server instances with separate project roots. By assigning a temporary MUX_ROOT to each worktree, you can run parallel tests with independent configurations and ports.

What causes cross-instance lockfile conflicts when running multiple dev-servers?▼

Cross-instance lockfile conflicts occur when multiple dev-server instances share the same MUX_ROOT. Provisioning each instance with its own temporary MUX_ROOT isolates the lockfiles, resolving the conflict and allowing parallel execution.

Do I need a specific Make target to start an isolated mux dev-server?▼

Yes, you need the Make target dev-server-sandbox to spin up a sandboxed MUX_ROOT and start a new isolated dev-server instance. This target manages environment overrides and sandbox defaults to isolate configurations.

Can I reuse provider configs across isolated dev-server sandboxes?▼

Yes, you can seamlessly reuse provider configs and project lists while keeping each dev-server sandbox isolated. This allows for consistent debugging and testing across parallel instances without losing your configuration setup.

Related Skills

Explore More Software Engineering Skills→
onchainengineeronchainengineer

dev-server-sandbox

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

Community
Intermediate
HouseGarofaloHouseGarofalo
3

haproxy

Configure HAProxy for load balancing, SSL termination, and health checks.

Official
Intermediate
codercoder
2.0k

dev-desktop-sandbox

Run isolated Mux desktop Electron instances with unique temporary MUX_ROOT directories.

Official
Advanced
onchainengineeronchainengineer

dev-desktop-sandbox

Launch isolated Electron Unix desktop sandboxes with per-instance UNIX_ROOTs and ports.

Community
Advanced