dev-desktop-sandbox

Name: dev-desktop-sandbox
Availability: InStock
Author: latticeHQ

Launches isolated Electron sandboxes for concurrent lattice desktop instances.

Updated Aug 23, 2026

Search Tags:#development #workspace #electron #sandbox #lattice #multi-instance #port-management

Ready to run

npx skills add https://github.com/latticeHQ/latticeWorkbench --skill dev-desktop-sandbox-latticehq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-desktop-sandbox
Source: https://github.com/latticeHQ/latticeWorkbench/tree/main/.lattice/skills/dev-desktop-sandbox
Command: npx skills add https://github.com/latticeHQ/latticeWorkbench --skill dev-desktop-sandbox-latticehq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run isolated Electron desktop instances without sharing a single lattice root, preventing conflicts between parallel sessions.

Core Features & Use Cases

Creates a fresh temporary LATTICE_ROOT for each sandbox.
Optionally copies provided config files (providers.jsonc, config.json) into the sandbox when present.
Allocates free ports for the Vite devserver and Electron remote debugging.
Executes make dev with LATTICE_ROOT and port environment variables to boot the sandboxed instance.
Waits for the devserver to become reachable, then runs make build-static to prepare dist for Electron.
Launches Electron with isolated environment variables to guarantee multiple concurrent instances.

Quick Start

Run make dev-desktop-sandbox to start a sandboxed Electron 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 Electron desktop instances in parallel?▼

Launch isolated Electron sandboxes using `make dev-desktop-sandbox` to create a temporary LATTICE_ROOT and assign unique Vite and remote debugging ports, preventing conflicts between parallel lattice desktop instances.

Why do my parallel Electron development sessions conflict with each other?▼

Parallel sessions conflict by sharing a single lattice root and port. The sandbox resolves this by generating a fresh temporary LATTICE_ROOT and allocating free ports for each concurrent instance.

Does the Electron sandbox support custom provider configurations?▼

Yes, the sandbox supports custom configurations by optionally copying provided `providers.jsonc` and `config.json` files into the fresh temporary LATTICE_ROOT directory when they are present before execution.

How does the sandbox prepare the Vite devserver for Electron?▼

The sandbox executes `make dev` with configured environment variables, waits until the Vite devserver becomes reachable, and then runs `make build-static` to prepare the dist output for the Electron instance.

Do I need a Makefile to use the isolated desktop sandbox?▼

Yes, a Makefile is required because the sandbox relies on the `dev-desktop-sandbox` target and executes `make dev` and `make build-static` commands to manage environment variables and boot the isolated instance.