What problem does it solve?
It prevents accidental actions in the wrong cmux workspace by scoping commands to the caller’s workspace, terminal/surface, panes, and sidebar state.
Core Features & Use Cases
- Caller-context scoping by default: Uses CMUX_WORKSPACE_ID, CMUX_SURFACE_ID, and CMUX_SOCKET_PATH to target the workspace that invoked the agent without relying on what is currently visually focused.
- Non-disruptive layout automation: Builds panes/surfaces additively and avoids focus-changing verbs unless explicitly requested.
- Workspace-scoped status and logs: Attaches progress, logs, and notifications to the correct workspace for a consistent sidebar experience.
- Helper-pane reuse pattern: Reuses (or creates exactly one) right-side helper pane for auxiliary output like logs, previews, and one-off terminals.
Quick Start
Ask the agent to “Set build status to running in the current cmux workspace and open a right-side helper terminal for log output without changing the user’s focus.”