skills.rest
manaflow-ai
manaflow-aiOFFICIAL
Explore all skills by this author →
GitHub

cmux-workspace

Scope automation to the current cmux workspace and its surfaces.

25.8k|2.2k|Updated Jan 28, 2026
Search Tags:#automation#context#workspace#panes#socket#cmux#surfaces
One-click install
npx skills add https://github.com/manaflow-ai/cmux --skill cmux-workspace-manaflow-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmux-workspace
Source: https://github.com/manaflow-ai/cmux/tree/main/skills/cmux-workspace
Command: npx skills add https://github.com/manaflow-ai/cmux --skill cmux-workspace-manaflow-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Work inside the current cmux workspace and terminal to scope automation and actions to the active context, preventing cross-workspace interference.

Core Features & Use Cases

  • Scope actions to the current caller workspace by default, including the current workspace, panes, and surfaces.
  • Target sockets, surfaces, and panes for cmux automation without leaving the active workspace.
  • Use for non-disruptive automation and coordination across the active cmux context.

Quick Start

Scope all automation to the current cmux workspace and its surfaces by default.

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 automation to the active workspace and prevent cross-workspace interference?▼

You can scope automation by constraining actions to the current cmux caller workspace and its surfaces, ensuring operations respect CMUX_WORKSPACE_ID, CMUX_SURFACE_ID, and CMUX_SOCKET_PATH to prevent cross-workspace interference.

What is a cmux workspace and when do I need to isolate automation context?▼

A cmux workspace is an isolated terminal context containing panes, surfaces, and sockets. You need to isolate automation context when running non-disruptive background tasks to prevent actions from leaking across workspace boundaries.

How do I target specific panes and surfaces for cmux automation without leaving the active workspace?▼

Target specific panes and surfaces by applying non-disruptive automation directly within the active workspace context, ensuring all socket and surface interactions respect the current CMUX_SURFACE_ID and CMUX_WORKSPACE_ID environment variables.

Can I explicitly target a different cmux workspace or surface than the active caller context?▼

Yes, you can explicitly target another workspace or surface, but by default all automation is constrained to the current cmux caller workspace to ensure non-disruptive coordination across the active context.

What environment variables does cmux workspace scoping rely on to constrain automation?▼

Cmux workspace scoping relies on CMUX_WORKSPACE_ID, CMUX_SURFACE_ID, and CMUX_SOCKET_PATH to identify and constrain all automation actions to the active caller context and its surfaces.

Related Skills

Explore More Software Engineering Skills→
deerawandeerawan
1

cmux-workspace

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

Community
Advanced
haryelramalhoharyelramalho

cmux-orchestration

Coordinate terminal agent workers across cmux panes and verify their reported changes.

Community
Advanced
tobyileetobyilee
24

cmux

Control cmux workspaces, panes, and browser surfaces via CLI.

Community
Advanced
delorenjdelorenj
14

zellij-layouts

Guide Zellij layout customization for panes, tabs, and session configurations.

Community
Intermediate