zmx

Manage long-lived dev processes with consistent session prefixes and lifecycle controls.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/opencode-config --skill zmx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zmx
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/zmx
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill zmx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev teams often run long-lived processes (servers, watchers, and tilt) that must persist across interactions. This Skill provides patterns to manage, isolate, and monitor these sessions to avoid port conflicts and unresponsive shells.

Core Features & Use Cases

  • Session rules to prevent duplicates and derive stable names
  • Start, monitor, and manage multiple processes with consistent prefixes
  • Lifecycle controls for cleaning up, attaching, and polling readiness
  • Use cases include starting dev servers, test runners, and file watchers in a project

Quick Start

Start a zmx session for your project and run development commands with automatic reuse and isolation.

Frequently Asked Questions about zmx

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage long-running dev servers to avoid port conflicts?▼

You can manage long-running dev servers by applying consistent session prefixes and lifecycle controls to isolate processes, which prevents port conflicts and unresponsive shells.

How do I run multiple development processes with tilt safely?▼

Running multiple development processes with tilt is handled by coordinating long-lived sessions using naming conventions and lifecycle controls to monitor, attach, and clean up tasks reliably.

What is the best way to prevent duplicate local dev server sessions?▼

Preventing duplicate local dev server sessions requires enforcing session rules that derive stable names and apply lifecycle controls, ensuring processes are safely isolated and reused.

Can I use this session management approach for multi-process development environments?▼

Yes, this session management approach applies to multi-process development environments by orchestrating local dev servers, watchers, and tilt across single or multiple projects with consistent prefixes.

Why does my unresponsive shell happen when starting file watchers and test runners?▼

Unresponsive shells happen when long-lived file watchers and test runners lack proper lifecycle controls, but enforcing consistent session prefixes and safer command execution reliably resolves this.