What problem does it solve?
Running multiple Compozy agents, QA runs, or parallel git worktrees on one machine causes runtime state collisions: shared COMPOZY_HOME directories, port conflicts on the daemon HTTP server, and clashing UDS or tmux sockets. This Skill provisions a dedicated runtime envelope per scenario so concurrent runs never interfere with each other or with the default ~/.compozy state.
Core Features & Use Cases
- Isolated Runtime Allocation: Generates a unique COMPOZY_HOME directory, a free 127.0.0.1 TCP port, a unique UDS path, and a dedicated tmux bridge socket, emitted as shell export statements ready for eval.
- Worktree-Aware Scoping: Optionally scopes the runtime home to Compozy/_worktrees/<slug>/.compozy when invoked from a parallel worktree, falling back to TMPDIR otherwise.
- Verified Teardown: Enforces mandatory process cleanup via a targeted teardown helper that proves ownership of the envelope and reports TEARDOWN_ALL_CLEAN=true, without touching unrelated labs.
- Use Case: An engineer creates a second worktree with make worktree-new SLUG=qa-fix, runs the allocator to get an isolated envelope, then executes E2E tests while another agent continues working in the main checkout.
Quick Start
Ask the agent to set up an isolated Compozy runtime for a parallel worktree or concurrent QA run, optionally providing a scenario slug for naming the envelope.