Drive agent terminal workspaces with Rmux
Use Rmux to create and automate cross-platform terminal sessions for agent CLIs, with tmux-compatible commands, typed SDKs, web sharing, and Claude Code teammate mode.
npx skills add agentskillexchange/skills --skill drive-agent-terminal-workspaces-with-rmux
Use Rmux when an operator needs to run, inspect, and automate terminal-native agent sessions across Linux, macOS, or Windows. The agent/operator creates Rmux sessions and panes, launches agent CLIs or TUI tools, drives them through tmux-compatible commands or typed Rust, Python, and TypeScript SDKs, captures pane state, and optionally shares the workspace through web-share. Invoke it instead of plain terminal tabs or OS-specific tmux setup when the workflow needs cross-platform terminal orchestration, programmatic pane control, or Claude Code teammate mode. The scope boundary is terminal workspace automation for agent and CLI operations; it is not a generic SDK listing or a replacement for the agent runtime itself.
What this skill actually does
Inputs and prerequisites: Rmux CLI, optional Rust SDK, Python librmux package, TypeScript @rmux/sdk package, optional Claude Code and web-share setup.
Setup notes: Install with brew install rmux, winget install rmux, scoop install rmux, choco install rmux, nix profile install github:Helvesec/rmux, cargo install rmux –locked, or a release package. Use rmux list-commands, rmux new-session, rmux split-window, rmux web-share, or rmux claude to run and supervise agent terminal workspaces.
Source and verification boundary: use https://rmux.io/docs/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.