Token导航 LogoToken导航

Agent Skill · 开发

cmux(cmux 控制)

cmux 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

cmux 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 21,023。

总安装 196周安装 8GitHub Stars 2下载 63核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cmux(cmux 控制)
来源仓库:https://github.com/jonmumm/skills
仓库路径:skills/cmux
安装命令:
npx skills add https://github.com/jonmumm/skills --skill cmux
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jonmumm/skills --skill cmux

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

cmux 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合围绕仓库状态和协作事项进行整理。适用于需要分析代码变更、跟踪 Issue 进展或管理 Pull Request 的开发协作场景。

通过 npx skills add 命令从 GitHub 仓库安装,需结合原始 README 确认具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。该技能归类为开发工具,主要用于控制相关的协作信息管理。

来源仓库内路径:skills/cmux

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jonmumm/skills --skill cmux;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

cmux 怎么安装?

在终端执行 npx skills add https://github.com/jonmumm/skills --skill cmux。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

cmux 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

cmux 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

cmux 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

cmux 用的人多吗?

公开数据是累计安装 196 次,近一周安装 8 次,下载 63 次,GitHub 2 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

cmux 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
cmux

cmux 控制 · 本页

1962接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

cmux

cmux is a native macOS terminal (Ghostty-based) with vertical tabs, notifications, and a scriptable CLI/socket API for managing multiple AI coding agent sessions in parallel. You use it to create isolated workspaces, monitor agent progress, send commands between workspaces, and build orchestration workflows.

When to use this skill

  • Running multiple Claude Code agents in parallel (beyond git worktrees)
  • /swarm or /nightshift needs terminal-level workspace management
  • User wants to spawn, monitor, or communicate between agent sessions
  • Setting up an orchestrator agent that controls other agents
  • Configuring notifications for agent completion/attention events

Hierarchy

Window (macOS window)
  └─ Workspace (sidebar entry, like a named "tab")
       └─ Pane (split region — Cmd+D right, Cmd+Shift+D down)
            └─ Surface (terminal or browser session within a pane)

Installation

brew tap manaflow-ai/cmux && brew install --cask cmux

CLI symlink (for access outside cmux terminals):

sudo ln -sf "/Applications/cmux.app/Contents/Resources/bin/cmux" /usr/local/bin/cmux

Core CLI commands

Workspace management

cmux list-workspaces                     # List all open workspaces (IDs, names, metadata)
cmux new-workspace                       # Create a new workspace
cmux select-workspace <ID>               # Switch to workspace by ID
cmux current-workspace                   # Get the active workspace
cmux close-workspace                     # Close current workspace
cmux rename-workspace <NAME>             # Rename current workspace

Surfaces and splits

cmux new-split right                     # Split pane right (also: left, up, down)
cmux new-split down                      # Split pane down
cmux list-surfaces                       # List all surfaces in current workspace
cmux focus-surface <ID>                  # Focus a specific surface by ID
cmux close-surface                       # Close current surface

Sending input to terminals

cmux send "your text here"               # Send text to focused terminal
cmux send-surface <ID> "text"            # Send text to a specific surface
cmux send-key enter                      # Send a key (enter, tab, escape, backspace, etc.)
cmux send-key-panel <ID> enter           # Send key to specific panel

Reading terminal output

cmux read-screen                         # Read current terminal screen content
cmux read-screen --workspace <ID>        # Read screen of a specific workspace

Notifications

cmux notify --title "Done" --body "Build complete"   # Send notification
cmux list-notifications                               # List all notifications
cmux clear-notifications                              # Clear all notifications

Sidebar metadata (status pills, progress bars, logs)

cmux set-status <KEY> <VALUE>            # Set a status pill on the sidebar tab
cmux clear-status <KEY>                  # Remove a status entry
cmux list-status                         # List all status entries
cmux set-progress 0.75                   # Set progress bar (0.0–1.0)
cmux clear-progress                      # Clear progress bar
cmux log info "Starting build..."        # Append log (levels: info, progress, success, warning, error)
cmux log success "All tests passed"
cmux log error "Build failed"

Browser automation

cmux browser goto <URL>                  # Navigate embedded browser
cmux browser back                        # Browser back
cmux browser forward                     # Browser forward
cmux browser reload                      # Reload page
cmux browser click <SELECTOR>            # Click element
cmux browser fill <SELECTOR> <TEXT>      # Fill form field
cmux browser get-text <SELECTOR>         # Get element text
cmux browser wait-for <SELECTOR>         # Wait for element to appear
cmux browser snapshot                    # Get accessibility tree
cmux browser screenshot                  # Capture page screenshot
cmux browser eval <JAVASCRIPT>           # Execute JS in browser

Windows

cmux list-windows                        # List all windows
cmux new-window                          # Create new window
cmux focus-window <ID>                   # Focus window
cmux close-window                        # Close window
cmux move-workspace-to-window <WID>      # Move workspace to another window

Environment variables

cmux auto-sets these in every terminal it spawns:

VariableDescription
CMUX_WORKSPACE_IDCurrent workspace ID
CMUX_SURFACE_IDCurrent surface ID
CMUX_SOCKET_PATHPath to the Unix socket

You can use these to identify which workspace you're in programmatically.

Socket API (v2 JSON protocol)

For programmatic access beyond the CLI, cmux exposes a Unix socket with a JSON protocol:

# Request (one JSON object per line)
echo '{"method":"workspace.list"}' | socat - UNIX-CONNECT:~/.cmux/socket

# Response
{"ok":true,"result":{...}}

Key v2 methods:

MethodDescription
workspace.listList all workspaces
workspace.createCreate workspace
workspace.selectSwitch to workspace
workspace.currentGet active workspace
surface.listList surfaces
surface.splitCreate split
surface.send_textSend text to surface
surface.send_keySend keystroke
notification.createSend notification
browser.open_splitOpen browser in split
browser.navigateNavigate browser

Socket access mode is configurable: off, cmuxOnly (default), allowAll.

Orchestrator pattern

One Claude Code agent acts as the orchestrator — it creates workspaces, spawns agents, monitors progress, and relays results.

Spawning a worker agent

# Create a named workspace
cmux new-workspace
cmux rename-workspace "feature-auth"

# Send a command to start Claude Code in that workspace
cmux send "claude --prompt 'Implement the auth middleware per the spec in docs/auth.md'"
cmux send-key enter

Monitoring a worker

# Read what's on the worker's screen without interrupting it
cmux read-screen --workspace <WORKSPACE_ID>

Sending instructions to a worker

# Send a follow-up instruction
cmux send-surface <SURFACE_ID> "now add integration tests for the auth routes"
cmux send-key-panel <PANEL_ID> enter

Checking all workspace statuses

cmux list-workspaces    # See all workspace names and IDs
# Then read-screen on each to check progress

Progress tracking via sidebar

Worker agents can update their sidebar status:

# From inside a worker workspace
cmux set-status phase "testing"
cmux set-progress 0.5
cmux log progress "Running integration tests (3/6 passing)"

The orchestrator (and the human) can see this in the sidebar without switching workspaces.

Integration with /swarm

Instead of (or alongside) git worktrees, /swarm can use cmux workspaces:

  1. Orchestrator workspace: Runs the swarm coordinator
  2. Feature workspace: Runs the Feature agent (claude --prompt "...")
  3. CRAP workspace: Runs the CRAP agent
  4. Mutation workspace: Runs the Mutation agent
  5. Acceptance workspace: Runs the Acceptance agent

Benefits over pure worktrees:

  • Visual: sidebar shows which agent is active, waiting, or done
  • Progress: each agent can cmux set-progress and cmux log its status
  • Notifications: agents send cmux notify when they need review
  • Cross-agent comms: orchestrator can read-screen and send to coordinate

Integration with /nightshift

Nightshift can use cmux to:

  1. Spawn a workspace per task from the backlog
  2. Monitor progress via read-screen between tasks
  3. Use cmux notify for the morning briefing
  4. Set sidebar status to show task completion state

Notification hooks for Claude Code

Wire Claude Code's hooks to cmux notifications:

// .claude/settings.json
{
  "hooks": {
    "notification": [
      {
        "command": "cmux notify --title \"$CLAUDE_NOTIFICATION_TITLE\" --body \"$CLAUDE_NOTIFICATION_BODY\""
      }
    ]
  }
}

Or use OSC sequences directly from within a terminal:

printf '\033]777;notify;Build Complete;All tests passing\033\\'

Keyboard shortcuts

ShortcutAction
Cmd+NNew workspace
Cmd+1–8Jump to workspace
Cmd+Shift+WClose workspace
Cmd+Shift+RRename workspace
Cmd+DSplit right
Cmd+Shift+DSplit down
Cmd+TNew surface (tab in pane)
Cmd+BToggle sidebar
Cmd+Shift+UJump to latest unread notification
Cmd+INotification panel
Opt+Cmd+ArrowsFocus pane directionally
Cmd+Shift+LOpen browser in split

Requirements

  • macOS 14.0+
  • Reads your existing ~/.config/ghostty/config for themes, fonts, colors

平台分布

Codex

35.68%
按下载量换算22

Claude

27.45%
按下载量换算17

Cursor

19.29%
按下载量换算12

Gemini CLI

8.73%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills