Runs long-lived, interactive, or remote commands in observable tmux sessions.
npx skills add https://github.com/MaxWolf-01/agents --skill tmux-maxwolf-01
Please help me install this Agent Skill. Skill: tmux Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/tmux Command: npx skills add https://github.com/MaxWolf-01/agents --skill tmux-maxwolf-01
job command to run, wait on, and clean up named background jobs like builds, test suites, and training runs. - Interactive panes: Drives REPLs, wizards, and sudo prompts via tmux send-keys and reads output with tmux capture-pane, with bin/tmux-wait-for-text to poll before typing. - Remote execution: Runs and monitors tmux sessions over ssh with proper quoting and keepalive settings, avoiding orphaned waiters. - Use Case: Start a database migration as a named job, poll its progress from scrollback, and hand the user a tmux attach command so they can step in if it stalls. ## Quick Start Use the tmux skill to run the test suite in a named session so I can watch its progress and attach to it if it hangs.High-intent search queries and answers about installing and using this skill.
Run it in a named tmux session or as a named job instead of a blocking Bash call. The session outlives the command, its scrollback stays readable, and you can poll output with tmux capture-pane or wait on completion with the job command.
Use tmux send-keys -t <session> -l 'command' followed by a separate send-keys with Enter. Poll first with bin/tmux-wait-for-text so input is not sent before the prompt appears.
Yes, quote the whole tmux command per ssh call, one command per connection. Wait on remote jobs with the job command on that host, and use ServerAliveInterval options so dead connections collapse quickly.
kill-server destroys the shared tmux server holding the user's shells, editors, and other agents' sessions. Kill only sessions you created with tmux kill-session -t <name>, or use a dedicated socket via tmux -L for throwaway test servers.
Commands that exit or fail on their own, like git status or cat, stay plain Bash. tmux is for anything that might not return, is worth observing mid-run, or is interactive.
Khamel83Execute remote commands over SSH for git sync, file transfer, and tmux jobs.
tenstorrentSummarize GitHub Actions nightly CI failures grouped by ownership area.
shanevRun long-running tasks in detached tmux sessions with persistent logs.
primovera12Automate unattended GSD sprint execution with multi-account rotation and pause/resume controls.