dev-server-sandbox

Create isolated LATTICE_ROOT environments and allocate free ports for parallel dev-server sandboxes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/latticeHQ/latticeWorkbench --skill dev-server-sandbox-latticehq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-server-sandbox
Source: https://github.com/latticeHQ/latticeWorkbench/tree/main/.lattice/skills/dev-server-sandbox
Command: npx skills add https://github.com/latticeHQ/latticeWorkbench --skill dev-server-sandbox-latticehq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run multiple isolated lattice dev-server instances by creating temporary LATTICE_ROOTs to enable parallel development and testing across worktrees.

Core Features & Use Cases

  • Creates fresh temporary LATTICE_ROOT directories for each sandboxed dev-server.
  • Copies optional provider and project configs (providers.jsonc and config.json) when present.
  • Allocates free ports and enables broad host access to support port-forwarding and multi-instance workflows.
  • Use Case: Run multiple parallel dev-server sessions from different git worktrees to test isolated configurations simultaneously.

Quick Start

Execute the sandbox to launch multiple isolated dev-server instances with automatic environment setup.

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 isolated dev-server instances in parallel?

To run multiple isolated dev-server instances in parallel, you can create temporary LATTICE_ROOT environments with automatically allocated free ports, allowing simultaneous development sessions across different git worktrees without configuration conflicts.

What is a dev-server sandbox and when do I need it?

A dev-server sandbox is a temporary, isolated environment that runs independent dev-server instances. You need it when testing multiple configurations simultaneously across different git worktrees or running parallel test workflows that require distinct ports.

How do I set up parallel testing across different git worktrees?

Set up parallel testing across git worktrees by launching a sandboxed dev-server that creates fresh temporary LATTICE_ROOT directories, copies optional provider and project configs, allocates free ports, and applies environment overrides for each instance.

Can I use existing provider and project configs with sandboxed dev-servers?

Yes, you can use existing provider and project configs. The sandbox automatically copies optional providers.jsonc and config.json files when present, applying them to the isolated LATTICE_ROOT environment before launching the server.

Does the sandbox handle port allocation for multi-instance dev-servers?

Yes, the sandbox handles port allocation by automatically selecting free ports for each dev-server instance. It enables broad host access to support port-forwarding and multi-instance workflows across parallel sandboxed environments.

What's the best way to test isolated configurations simultaneously?

The best way to test isolated configurations simultaneously is creating temporary LATTICE_ROOT directories for each dev-server sandbox, which allocates free ports and launches independent instances with specific environment overrides from different git worktrees.