cmux CLI

Use the cmux CLI as the default interface. Treat every command as acting on a specific workspace, panel, or surface. Observable behavior is the anchor: state the intended target, run the command, then query the cmux state that can prove the result.

Establish Context

1. Run cmux ping. If it fails, report that cmux is unavailable or not responding. Do not install it, change socket settings, or use another terminal manager unless the user asks.
2. Run cmux identify --json to capture the focused window, workspace, panel, and surface. Use cmux current-workspace --json or cmux list-workspaces --json when the request names a workspace rather than the focused one.
3. For a non-focused target, resolve its identifier from JSON output and pass the documented scope flag: --window, --workspace, or --surface. Request --id-format both if a reference ID and UUID must be distinguished.

Say: “The observable behavior I will verify is that surface <id> receives the requested input.” Never infer the target from a previous command when a fresh query can establish it.

Execute the Requested Operation

Use one cmux command per shell call. Prefer JSON output when parsing IDs or reporting state. Read references/cli-reference.md from this skill's directory when an operation is uncommon or its exact flags are not below.

Workspace and Panels