← Back to Skills Marketplace
111
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install smux
Description
Cross-pane messaging for tmux. Use `tmux-bridge` command to send messages between panes labeled p1, p2, p3...
Usage Guidance
Do not install or run this skill blindly. The SKILL.md expects a third-party 'tmux-bridge' CLI but the skill package provides no binary, no install instructions, and no source/homepage to vet. Before using: (1) obtain and review the tmux-bridge binary/source from a trusted location (or ask the author for a link); (2) inspect what tmux-bridge does (especially whether it reads other panes, writes files, or contacts networks); (3) do not append anything to ~/.tmux.conf without reviewing the auto-label content; (4) if you allow an agent to run this skill autonomously, be aware it is instructed to auto-reply to incoming 'pending' messages — that can cause automatic cross-pane messaging and potential data leakage; and (5) prefer skills that declare all required binaries and provide an install or a verifiable homepage/source. If you can obtain the tmux-bridge source for review, rescan the skill with that included — that information would likely change the assessment.
Capability Analysis
Type: OpenClaw Skill
Name: smux
Version: 1.0.0
The 'smux' skill bundle is a utility for managing multi-agent collaboration within tmux panes. It defines a communication protocol using a `tmux-bridge` CLI tool (documented in SKILL.md and tmux-bridge.md) to send, receive, and track messages between panes labeled p1, p2, etc. The instructions include security best practices, such as mandating absolute paths for scripts to prevent path hijacking, and the suggested modification to `~/.tmux.conf` is a standard configuration step for tmux utilities with no evidence of malicious intent or data exfiltration.
Capability Tags
Capability Assessment
Purpose & Capability
The skill claims to provide a tmux-based cross-pane messaging CLI (tmux-bridge). The registry metadata only requires 'tmux' but the SKILL.md repeatedly instructs the agent to run a separate 'tmux-bridge' binary. That binary is not included, not declared as a required dependency, and there is no homepage or source repository to verify what it does. This mismatch (declared requirements vs. actual instructions) is incoherent and potentially risky.
Instruction Scope
Runtime instructions tell the agent to run tmux-bridge commands (send, pending, reply) and to append auto-label configuration into ~/.tmux.conf and then source it. Modifying ~/.tmux.conf is a non-trivial side effect and should be explicit/trusted. References in the tmux fallback docs to commands like 'capture-pane -p' indicate the ability to read pane contents; while SKILL.md doesn't explicitly instruct arbitrary pane captures, the provided fallbacks could be used to read other panes' output. The skill also prescribes agents automatically replying to pending messages, which could cause automatic cross-agent messaging or unintended disclosure if deployed autonomously.
Install Mechanism
There is no install spec (instruction-only), which minimizes direct file-writing by the skill itself. However, because the skill expects an external 'tmux-bridge' CLI that is neither bundled nor linked, an operator or agent may try to obtain or execute that binary from elsewhere — the absence of a trusted install source or homepage is a practical and security concern.
Credentials
The skill requests no environment variables or credentials. Requiring only the 'tmux' binary (but in practice also needing 'tmux-bridge') is proportionate to a tmux-integration skill — the main issue is the missing/undeclared tmux-bridge artifact, not overbroad credential requests.
Persistence & Privilege
always:false (normal). The skill instructs agents to modify ~/.tmux.conf (persistent user config), which is a write to user configuration and should be performed only with explicit consent. Also the agent collaboration rules encourage automatic replies to other panes; combined with autonomous agent invocation this could lead to automatic cross-pane messaging loops or unintended actions. This is a behavioral risk rather than a direct privilege escalation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install smux - After installation, invoke the skill by name or use
/smux - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release with streamlined, label-based tmux agent coordination.
- Added `tmux-bridge` as the primary interface for cross-pane messaging using `p1`, `p2`, `p3` labels—no need to remember pane IDs.
- Introduced commands for launching, killing sessions, sending messages with/without expecting replies, and replying to pending tasks.
- Simplified agent collaboration guidelines: always check `pending` before replying, and avoid unnecessary or empty acknowledgements.
- Provided automated pane labeling and easy auto-label setup via tmux.conf.
- Documented best practices for agent-to-agent task delegation and session management.
v2.1.1
Improve ClawHub-facing docs with clearer onboarding, common usage patterns, follow-up workflow, and practical defaults.
v2.1.0
Prefer installed tmux-bridge, forbid relative paths, add explicit --expect-reply/--no-reply flow, and add pending/check follow-up commands.
Metadata
Frequently Asked Questions
What is Smux?
Cross-pane messaging for tmux. Use `tmux-bridge` command to send messages between panes labeled p1, p2, p3... It is an AI Agent Skill for Claude Code / OpenClaw, with 111 downloads so far.
How do I install Smux?
Run "/install smux" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Smux free?
Yes, Smux is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Smux support?
Smux is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin, linux).
Who created Smux?
It is built and maintained by mkuiwu (@mkuiwu); the current version is v1.0.0.
More Skills