Manages and automates named tmux sessions for workflows across multiple projects.
npx skills add https://github.com/phuetz/code-buddy --skill tmux-sessions
Please help me install this Agent Skill. Skill: tmux-sessions Source: https://github.com/phuetz/code-buddy/tree/main/.codebuddy/skills/bundled/tmux-sessions Command: npx skills add https://github.com/phuetz/code-buddy --skill tmux-sessions
This Skill helps developers manage and automate multiple tmux sessions, reducing context switching and improving parallel workstreams.
Run the following to create a background development server in a named tmux session: tmux new-session -d -s dev-server Attach to the session: tmux attach -t dev-server Start a watcher in a second session: tmux new-session -d -s logs Send commands to the background session: tmux send-keys -t dev-server 'npm run dev' Enter Clean up: tmux kill-session -t dev-server tmux kill-session -t logs
High-intent search queries and answers about installing and using this skill.
You can manage multiple tmux sessions by creating, attaching, detaching, and killing named sessions to run background servers and monitor logs side-by-side. This orchestration keeps parallel workstreams organized across different projects.
You send commands to a background tmux session using the send-keys command with the target session name. For example, use `tmux send-keys -t dev-server 'npm run dev' Enter` to execute commands within a detached session without attaching to it.
The best way to run parallel workflows in tmux is by creating detached named sessions for each task, such as one for a dev server and another for logs. This allows you to monitor tests, servers, and logs side-by-side without context switching.
Yes, you need tmux installed on your host system to automate session workflows. The skill requires the tmux multiplexer to be present on the host to execute commands for quick session creation, attachment, and lifecycle control.
To create a detached tmux session for a background server, run `tmux new-session -d -s dev-server`. You can later attach to this running session using the command `tmux attach -t dev-server` to view its output.
To kill a specific tmux session and clean up background processes, use the command `tmux kill-session -t <session-name>`. This terminates the targeted session and ends the parallel workflows running inside it.
Neneka448Manage tmux sessions and automate keyboard/mouse input.
ThrookieConvert site analysis results into SKILL.md documents, tests, and code templates.
zhcndocSend keystrokes and capture pane output in tmux sessions.
bruno-garciaManage interactive and long-running commands in isolated tmux sessions.
