cmux-workspace

Scope cmux automation to the caller's workspace and surface.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill cmux-workspace-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmux-workspace
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/cmux-workspace
Command: npx skills add https://github.com/selfagency/agentsy --skill cmux-workspace-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.”

Frequently Asked Questions about cmux-workspace

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

FAQPage Schema
How do I scope cmux workspace automation to the current terminal surface?

Scope cmux workspace automation by honoring CMUX_WORKSPACE_ID, CMUX_SURFACE_ID, and CMUX_SOCKET_PATH environment variables to target the caller's context without relying on visual focus.

Why do my terminal automation scripts send commands to the wrong cmux pane?

Commands target the wrong cmux pane when they rely on visual focus instead of caller context. Use explicit --workspace and --surface flags for mutating actions to ensure correct terminal surface targeting.

Can I automate cmux pane management without changing the user's current focus?

Yes, non-disruptive layout automation builds panes and surfaces additively while avoiding focus-changing verbs unless the user explicitly requests them, keeping the current terminal context stable.

What is the best way to maintain sidebar logs in a specific cmux workspace?

Maintain sidebar logs by scoping progress, notifications, and status updates to the correct workspace using CMUX_WORKSPACE_ID, ensuring a consistent sidebar experience tied to the caller's environment.

How do I reuse a right-side helper pane for auxiliary terminal output?

Reuse a right-side helper pane by leveraging the helper-pane pattern, which creates exactly one auxiliary terminal surface for logs, previews, and one-off commands without disrupting the main workspace layout.

Do I need explicit flags for mutating actions in cmux workspace management?

Yes, mutating actions require explicit --workspace and --surface flags to prevent accidental actions in the wrong cmux workspace and ensure commands execute in the intended terminal context.