Skill

cmux Workspace Orchestration

Install
1
Install the plugin
$
npx claudepluginhub jack-michaud/faire --plugin cmux

Want just this skill?

Add to a custom plugin, then install with one command.

Description

This skill should be used when the user asks to "set up a dev environment", "create a workspace", "open a browser pane", "split terminal", "spin up frontend and backend", "use cmux", "manage cmux panes", "run commands in cmux", or mentions cmux workspaces, panes, surfaces, or browser automation. Provides workflow guidance for orchestrating multi-pane development environments with terminal and browser surfaces.

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets
View in Repository
resources/workspace-survey.md
Skill Content

cmux Workspace Orchestration

cmux is a terminal multiplexer application for macOS with a rich CLI for managing windows, workspaces, panes, browser surfaces, and sidebar logging. It is controlled via a Unix socket at /tmp/cmux.sock.

Core Concepts

cmux organizes its hierarchy as: Window > Workspace > Pane > Surface (Tab)

  • Window: Top-level OS window
  • Workspace: A named layout within a window (like tmux sessions). Visible in the sidebar.
  • Pane: A split region within a workspace. Each pane contains one or more surfaces as tabs.
  • Surface: A single terminal or browser tab within a pane. Referenced as surface:<n>.

All commands use ref format by default: workspace:1, pane:2, surface:3.

Environment variables CMUX_WORKSPACE_ID and CMUX_SURFACE_ID are auto-set in cmux terminals and serve as defaults for --workspace and --surface flags.

CLI Reference

Run cmux --help for the full command list. Run cmux <command> --help for details on any specific command. Use --json flag on most commands for machine-readable output.

Tips

  • Use cmux identify --json to discover the current workspace, pane, and surface context.
  • After creating splits, use cmux list-panes and cmux list-pane-surfaces to discover new surface refs.
  • Use cmux capture-pane --lines <n> to read terminal output and detect when processes are ready.
  • Use cmux log with levels (progress, success, error) and cmux notify for sidebar visibility.
  • Browser snapshot --interactive returns an accessibility tree ideal for understanding page structure.
  • cmux send uses \n for Enter and \t for Tab in the text argument.

Workflows

Successful workflows are documented as reference files. Check resources/ for proven patterns.

Resources

Custom docs written on cmux topics:

  • resources/workspace-survey.md — How to survey the current workspace state at the start of a session
Stats
Stars5
Forks0
Last CommitMar 22, 2026
Actions

Similar Skills

cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.4k