skills.rest
neilmovva
neilmovvaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-desktop-sandbox

Launch isolated MUX desktop Electron instances with temporary MUX_ROOT directories and free ports.

Updated Feb 24, 2026
Search Tags:#testing#development#isolation#electron#sandbox#mux
One-click install
npx skills add https://github.com/neilmovva/mux --skill dev-desktop-sandbox-neilmovva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-desktop-sandbox
Source: https://github.com/neilmovva/mux/tree/main/.mux/skills/dev-desktop-sandbox
Command: npx skills add https://github.com/neilmovva/mux --skill dev-desktop-sandbox-neilmovva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of running multiple, isolated MUX desktop (Electron) instances simultaneously for development purposes, preventing conflicts and simplifying the development workflow.

Core Features & Use Cases

  • Isolated Environments: Creates temporary, independent MUX_ROOT directories for each instance.
  • Port Management: Automatically assigns free ports for Vite dev servers and Electron debugging.
  • Configuration Preservation: Optionally copies essential configuration files like providers.jsonc and config.json into the sandbox.
  • Use Case: A developer needs to test different configurations or branches of the MUX application concurrently without interfering with each other or their main development setup.

Quick Start

Execute the command make dev-desktop-sandbox to launch an isolated MUX desktop instance.

Frequently Asked Questions about dev-desktop-sandbox

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

FAQPage Schema
How do I run multiple isolated MUX desktop instances for development?▼

You can run isolated MUX desktop instances by using a sandbox approach that creates temporary MUX_ROOT directories and automatically assigns free ports for Vite dev servers and Electron debugging.

What is the best way to test different branches of an Electron app concurrently?▼

The best way to test different branches concurrently is using an isolated desktop sandbox that prevents conflicts by assigning independent temporary directories and free ports for each instance.

Why do my parallel Electron development instances have port conflicts?▼

Parallel Electron instances have port conflicts because they default to the same network ports; isolating them requires automatically assigning free ports for Vite dev servers and Electron debugging.

Can I preserve configuration files when launching an isolated Electron sandbox?▼

Yes, you can preserve configuration when launching an isolated Electron sandbox by optionally copying essential files like providers.jsonc and config.json into the temporary MUX_ROOT directory.

Does MUX_E2E=1 enhance Electron isolation in a development sandbox?▼

Yes, setting MUX_E2E=1 enhances Electron isolation within the development sandbox, providing stricter boundaries for testing parallel MUX instances during complex workflows.

When should I use a clean state for parallel MUX instance testing?▼

You should use a clean state for parallel MUX instance testing when you need to verify baseline behavior without previous data interference, or when utilizing specific seeding roots for targeted validation.

Related Skills

Explore More Software Engineering Skills→
lpjhelderlpjhelder

forge-setup

Install and configure kronon-forge with Node.js and npm.

Community
Intermediate
jdiegosierrajdiegosierra
1

playwright

Automate browser interactions and end-to-end testing workflows for web applications.

Community
Advanced
codercoder
2.0k

dev-desktop-sandbox

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

Official
Advanced
Fantasia1999Fantasia1999

git-worktree-manager

Manage Git worktrees with deterministic port allocation and safe cleanup.

Community
Advanced