dev-server-sandbox

Launch isolated Mux development server instances with temporary MUX_ROOT directories and port assignments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of running multiple instances of the Mux dev server simultaneously, which is normally restricted due to a single lockfile.

Core Features & Use Cases

  • Isolated Environments: Creates temporary, isolated MUX_ROOT directories for each dev server instance.
  • Port Management: Automatically assigns free ports for the backend and Vite development server.
  • Configuration Seeding: Optionally copies providers.jsonc and config.json from a specified or default MUX_ROOT.
  • Use Case: Developers can run multiple Mux instances for testing different branches or configurations in parallel without conflicts.

Quick Start

Execute the make dev-server-sandbox command to start a new isolated Mux development 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 multiple Mux dev servers in parallel?

To run multiple isolated Mux dev servers, execute the `make dev-server-sandbox` command. This creates a temporary MUX_ROOT directory and automatically assigns free ports for the backend and Vite development server instances.

Why does my Mux development server fail to start when another instance is running?

Your Mux development server fails to start due to a single lockfile limitation that restricts running multiple instances. This Skill addresses the limitation by creating temporary MUX_ROOT directories for each dev server instance.

Can I seed provider and project configurations when launching an isolated dev server?

Yes, you can seed provider and project configurations when launching an isolated dev server. The Skill optionally copies `providers.jsonc` and `config.json` from a specified or default MUX_ROOT into the new temporary directory.

How does port management work for parallel Mux development servers?

Port management for parallel Mux development servers works by automatically assigning free ports for the backend and Vite development server. This prevents network conflicts when running multiple isolated instances simultaneously.

What is the best way to test different Mux branches simultaneously without configuration conflicts?

The best way to test different Mux branches simultaneously is to use an isolated dev server sandbox. Developers can run multiple Mux instances in parallel by creating temporary MUX_ROOT directories and managing port assignments.