// Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)
| name | dev-server-sandbox |
| description | Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports) |
dev-server sandbox instancesmake dev-server starts the mux backend server, which uses a lockfile at:
<MUX_ROOT>/server.lock (defaults to ~/.mux-dev/server.lock in development)This means you can only run one dev server per mux root directory.
This skill documents the repo workflow for starting multiple dev-server instances in parallel (including from different git worktrees) by giving each instance its own temporary MUX_ROOT.
make dev-server-sandbox
MUX_ROOT directoryproviders.jsonc (provider config)config.json (project list)BACKEND_PORT, VITE_PORT)MUX_ENABLE_TUTORIALS_IN_SANDBOX=1 opts back in)VITE_ALLOWED_HOSTS=all) so it works behind port-forwarding domainsmake dev-server with those env overrides# Start with a clean instance (do not copy providers or projects)
make dev-server-sandbox DEV_SERVER_SANDBOX_ARGS="--clean-providers --clean-projects"
# Skip copying providers.jsonc
make dev-server-sandbox DEV_SERVER_SANDBOX_ARGS="--clean-providers"
# Clear projects from config.json (preserves other config)
make dev-server-sandbox DEV_SERVER_SANDBOX_ARGS="--clean-projects"
# Use a specific root to seed from (defaults to ~/.mux-dev then ~/.mux)
SEED_MUX_ROOT=~/.mux-dev make dev-server-sandbox
# Keep the sandbox root directory after exit (useful for debugging)
KEEP_SANDBOX=1 make dev-server-sandbox
# Pin ports (must be different)
BACKEND_PORT=3001 VITE_PORT=5174 make dev-server-sandbox
# Re-enable tutorials for sandbox dogfooding
MUX_ENABLE_TUTORIALS_IN_SANDBOX=1 make dev-server-sandbox
# Override which make binary to use
MAKE=gmake make dev-server-sandbox
providers.jsonc may contain API keys.secrets.json.Terminal-Bench integration for Mux agent benchmarking and failure analysis
Regenerate high-resolution README screenshots from Storybook stories. Use this skill when Chromatic detects visual diffs in any story under "Docs/README Screenshots", or when story data/layout changes require updated documentation assets. Triggers on: Chromatic visual regressions in readme screenshot stories, changes to App.readmeScreenshots.stories.tsx, changes to mockFactory.ts that affect screenshot stories, or explicit user request to update README images.
Guidelines for creating and managing Pull Requests in this repo
Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)
Testing doctrine, commands, and test layout conventions
Connects Mux mobile (Expo web/native) to an isolated dev-server sandbox with deterministic port setup, backend pairing, and Chrome MCP interaction. Use when implementing or validating mobile features against a sandboxed Mux backend.