dev-desktop-sandbox

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables running multiple isolated Electron-based Unix desktop sandboxes by creating per-instance UNIX_ROOT environments and assigning separate ports, preventing cross-instance state conflicts during development.

Core Features & Use Cases

  • Per-instance UNIX_ROOT isolation: each sandbox maintains its own configuration, sessions, and worktrees.
  • Parallel desktop experimentation: run several Electron desktop instances concurrently across different git worktrees.
  • Seeded sandboxes: optionally seed from existing providers/configs and launch Electron with deterministic settings.

Quick Start

Run the sandbox with: make dev-desktop-sandbox

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 Electron desktop instances in parallel without state conflicts?

Running multiple Electron desktop instances in parallel without state conflicts requires per-instance UNIX_ROOT isolation. This skill automates assigning separate ports and creating isolated environments across different git worktrees to prevent cross-instance interference.

How do I isolate Unix desktop sandboxes for parallel development across different worktrees?

Isolating Unix desktop sandboxes for parallel development involves creating per-instance UNIX_ROOT environments and separate port allocations. This skill automates launching isolated Electron instances to prevent cross-instance interference across different worktrees.

What is a UNIX_ROOT environment and when do I need it for Electron development?

A UNIX_ROOT environment is an isolated directory structure maintaining its own configuration, sessions, and worktrees for a specific desktop sandbox. You need it when running multiple Electron instances concurrently to prevent cross-instance state conflicts.

Can I launch Electron sandboxes with separate port allocations using bunx?

Yes, you can launch Electron sandboxes with separate port allocations using bunx. This skill automates the process by assigning unique ports and configuring the appropriate environment variables for each isolated instance.

Does this sandbox automation support seeded configurations from existing providers?

Yes, this sandbox automation supports seeded configurations from existing providers. You can optionally seed sandboxes from existing configs and launch Electron with deterministic settings across your parallel development workflows.

What are the limitations of running isolated Unix desktop instances concurrently?

Limitations of running isolated Unix desktop instances concurrently include managing separate port allocations and environment configurations for each sandbox. This skill targets Unix-based Electron workflows and requires manual coordination of worktree assignments.