cmux

Manage terminal and Playwright browser surfaces from a unified CLI.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/v36372/pi-stuff --skill cmux-v36372
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux
Source: https://github.com/v36372/pi-stuff/tree/main/skills/cmux
Command: npx skills add https://github.com/v36372/pi-stuff --skill cmux-v36372

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

cmux lets you run and observe multiple terminal sessions and embedded browser surfaces from a single CLI, enabling coordinated workflows for dev servers, test runners, and long‑running tasks.

Core Features & Use Cases

  • Create and manage surfaces (terminals) within the current workspace to keep tasks grouped.
  • Open and control a Playwright-powered browser surface for automated testing, page interactions, and verification.
  • Read outputs, send commands, and orchestrate multi‑process tasks across terminals and browser surfaces.

Quick Start

Open a terminal surface, start a dev server, and open a browser surface to verify end-to-end orchestration.

Frequently Asked Questions about cmux

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

FAQPage Schema
How do I orchestrate multiple terminal sessions from a single CLI?

You can orchestrate multiple terminal sessions by creating and managing terminal surfaces within a shared workspace, allowing you to start dev servers, send commands, and read outputs from one unified CLI.

Can I control a browser surface for automated testing alongside terminal workflows?

Yes, you can open and control a Playwright-powered browser surface for automated testing and page interactions, coordinating browser-driven verification alongside your terminal workflows.

What is a terminal workspace and when do I need it for devops automation?

A terminal workspace groups multiple terminal surfaces into a shared environment for devops automation, enabling you to coordinate multi-process workflows like running test runners and dev servers simultaneously.

Does terminal orchestration work for coordinating long-running tasks and test runners?

Yes, terminal orchestration supports coordinating long-running tasks and test runners by allowing you to run, observe, and manage multiple processes concurrently across grouped terminal surfaces.

What is the best way to manage multi-process workflows across terminals and a browser?

The best way to manage multi-process workflows is using a unified CLI to create terminal and browser surfaces, send commands, read outputs, and verify end-to-end orchestration across a shared workspace.

Why use a unified CLI for terminal and browser orchestration instead of separate tools?

Using a unified CLI for terminal and browser orchestration lets you observe and control multi-process workflows from a single interface, preventing context switching when running dev servers, tests, and browser verification.