cmux-workspace

Scope cmux automation to the caller workspace, surface, and socket context.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill cmux-workspace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmux-workspace
Source: https://github.com/deerawan/dotfiles/tree/main/agents/skills/cmux-workspace
Command: npx skills add https://github.com/deerawan/dotfiles --skill cmux-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents cmux automation from acting on the wrong window, workspace, pane, or terminal by consistently targeting the caller-scoped cmux context.

Core Features & Use Cases

  • Caller-scoped workspace targeting: Uses CMUX_WORKSPACE_ID and CMUX_SURFACE_ID as the default anchors to keep actions aligned with the invoking workspace and terminal.
  • Non-disruptive layout automation: Builds panes and surfaces additively and avoids speculative focus changes, so the user’s attention and visible layout are not disturbed.
  • Right-side helper pane management: Reuses an existing right-side helper pane when available; otherwise creates exactly one to host previews, logs, TUIs, or one-off shells.
  • Workspace-scoped status and sidebar output: Attaches progress, logs, and notifications to the current workspace for accurate sidebar reflection.

Quick Start

Use cmux-workspace to identify the current caller workspace and surface, then run workspace-scoped commands and send output to the caller surface while optionally creating or reusing a right-side helper pane for logs.

Frequently Asked Questions about cmux-workspace

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

FAQPage Schema
How do I scope terminal orchestration commands to a specific workspace?▼

Scoping terminal orchestration to a specific workspace requires anchoring commands to caller-provided identifiers like CMUX_WORKSPACE_ID and CMUX_SURFACE_ID. This ensures automation targets the correct terminal surface and prevents actions from executing on the wrong window or pane.

Why does my terminal automation route output to the wrong pane?▼

Terminal automation routes output incorrectly when it lacks socket targeting context. By preferring CMUX_SOCKET_PATH and workspace-scoped anchors, commands bind to the invoking caller surface, ensuring status logs and notifications reflect in the correct sidebar.

How do I build terminal pane layouts without disrupting the current focus?▼

Building pane layouts non-disruptively requires adding surfaces additively and avoiding speculative focus changes. Restrict focus-changing verbs to explicit user requests so the visible layout and user attention remain undisturbed during orchestration.

Can I reuse an existing right-side helper pane for sidebar logs?▼

You can reuse an existing right-side helper pane for sidebar logs and previews. If a helper pane is unavailable, the automation creates exactly one to host TUIs, logs, or one-off shells without spawning duplicates.

What environment variables are needed for workspace-scoped terminal targeting?▼

Workspace-scoped terminal targeting requires CMUX_WORKSPACE_ID, CMUX_SURFACE_ID, and CMUX_SOCKET_PATH. These variables anchor automation to the caller workspace, ensuring pane routing and auxiliary output routing execute within the correct socket context.