tmux-processes
Scannednpx machina-cli add skill aiskillstore/marketplace/tmux-processes --openclawtmux Process Management
Interactive Shell Requirement
Use send-keys pattern for reliable shell initialization. Creating a session spawns an interactive shell automatically. Use send-keys to run commands within that shell, ensuring PATH, direnv, and other initialization runs properly.
# WRONG - inline command bypasses shell init, breaks PATH/direnv
tmux new-session -d -s "$SESSION" -n main 'tilt up'
# CORRECT - create session, then send command to interactive shell
tmux new-session -d -s "$SESSION" -n main
tmux send-keys -t "$SESSION:main" 'tilt up' Enter
Session Naming Convention
Always derive session name from the project:
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
For multiple processes in one project, use windows not separate sessions:
- Session:
myapp - Windows:
server,tests,logs
Starting Processes
Single Process
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Create session with named window, then send command
tmux new-session -d -s "$SESSION" -n main
tmux send-keys -t "$SESSION:main" '<command>' Enter
Idempotent Start
Check if already running before starting:
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
if ! tmux has-session -t "$SESSION" 2>/dev/null; then
tmux new-session -d -s "$SESSION" -n main
tmux send-keys -t "$SESSION:main" '<command>' Enter
else
echo "Session $SESSION already exists"
fi
Adding Windows to Existing Session
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Add a new window if it doesn't exist
if ! tmux list-windows -t "$SESSION" -F '#{window_name}' | grep -q "^server$"; then
tmux new-window -t "$SESSION" -n server
tmux send-keys -t "$SESSION:server" 'npm run dev' Enter
else
echo "Window 'server' already exists"
fi
Multiple Processes (Windows)
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Create session with first process
tmux new-session -d -s "$SESSION" -n server
tmux send-keys -t "$SESSION:server" 'npm run dev' Enter
# Add more windows
tmux new-window -t "$SESSION" -n tests
tmux send-keys -t "$SESSION:tests" 'npm run test:watch' Enter
tmux new-window -t "$SESSION" -n logs
tmux send-keys -t "$SESSION:logs" 'tail -f logs/app.log' Enter
Monitoring Output
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Last 50 lines from first window
tmux capture-pane -p -t "$SESSION" -S -50
# From specific window
tmux capture-pane -p -t "$SESSION:server" -S -50
# Check for errors
tmux capture-pane -p -t "$SESSION" -S -100 | rg -i "error|fail|exception"
# Check for ready indicators
tmux capture-pane -p -t "$SESSION:server" -S -50 | rg -i "listening|ready|started"
Lifecycle Management
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# List all sessions (see what exists)
tmux ls
# List windows in current session
tmux list-windows -t "$SESSION"
# Kill only this project's session
tmux kill-session -t "$SESSION"
# Kill specific window
tmux kill-window -t "$SESSION:tests"
# Send keys to a window (e.g., Ctrl+C to stop)
tmux send-keys -t "$SESSION:server" C-c
Isolation Rules
- Never use
tmux kill-server - Never kill sessions not matching current project
- Always derive session name from git root or pwd
- Always verify session name before kill operations
- Other Claude Code instances may have their own sessions running
When to Use tmux
| Scenario | Use tmux? |
|---|---|
tilt up | Yes, always |
Dev server (npm run dev, rails s) | Yes |
File watcher (npm run watch) | Yes |
Test watcher (npm run test:watch) | Yes |
| Database server | Yes |
One-shot build (npm run build) | No |
| Quick command (<10s) | No |
| Need stdout directly in conversation | No |
Checking Process Status
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Check session exists
tmux has-session -t "$SESSION" 2>/dev/null && echo "session exists" || echo "no session"
# List windows and their status
tmux list-windows -t "$SESSION" -F '#{window_name}: #{pane_current_command}'
# Check if specific window exists
tmux list-windows -t "$SESSION" -F '#{window_name}' | grep -q "^server$" && echo "server window exists"
Restarting a Process
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Send Ctrl+C then restart command
tmux send-keys -t "$SESSION:server" C-c
sleep 1
tmux send-keys -t "$SESSION:server" 'npm run dev' Enter
Common Patterns
Start dev server if not running
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
if ! tmux has-session -t "$SESSION" 2>/dev/null; then
tmux new-session -d -s "$SESSION" -n server
tmux send-keys -t "$SESSION:server" 'npm run dev' Enter
echo "Started dev server in tmux session: $SESSION"
elif ! tmux list-windows -t "$SESSION" -F '#{window_name}' | grep -q "^server$"; then
tmux new-window -t "$SESSION" -n server
tmux send-keys -t "$SESSION:server" 'npm run dev' Enter
echo "Added server window to session: $SESSION"
else
echo "Server already running in session: $SESSION"
fi
Wait for server ready
SESSION=$(basename $(git rev-parse --show-toplevel 2>/dev/null) || basename $PWD)
# Poll for ready message
for i in {1..30}; do
if tmux capture-pane -p -t "$SESSION:server" -S -20 | rg -q "listening|ready"; then
echo "Server ready"
break
fi
sleep 1
done
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/0xbigboss/tmux-processes/SKILL.mdView on GitHub Overview
tmux-processes provides practical patterns for running and managing long-lived tasks inside tmux sessions. It covers how to initialize a reliable interactive shell, derive per-project session naming, and organize multiple processes as windows for a smooth lifecycle. This approach is ideal for dev servers, watchers, Tilt, or any process that should outlive the current conversation.
How This Skill Works
Run commands inside an interactive tmux shell by first creating a session and then sending keys to the window, ensuring initialization like PATH and direnv are applied. Use a per-project session and named windows to host related processes, such as server, tests, and logs. Include idempotent start checks to avoid duplicating sessions and simplify lifecycle management.
When to Use It
- Starting dev servers or file watchers that should stay alive beyond a single terminal session
- Ensuring proper shell initialization by running commands in an interactive tmux shell
- Managing multiple related processes for a project by using windows within a single session
- Starting processes idempotently to avoid recreating existing sessions
- Isolating and controlling only your project's tmux session for safe lifecycle management
Quick Start
- Step 1: Derive SESSION from the project root (git root or current directory)
- Step 2: Create a tmux session for the project and launch the main window to run your command
- Step 3: Add additional windows (server, tests, logs) as needed and monitor output
Best Practices
- Derive the session name from the git root or current directory to keep projects isolated
- Create the session first, then send commands to the main window to preserve init
- Use tmux has-session to implement idempotent starts and avoid duplicates
- Add separate windows (e.g., server, tests, logs) for clear process separation
- Avoid using tmux kill-server and only terminate the specific project session
Example Use Cases
- Start a single long-running process in a dedicated tmux session and run the main command in the main window
- Add a server window and run npm run dev for the dev server
- Add a tests window and run npm run test:watch to monitor tests
- Add a logs window and tail -f logs/app.log to watch output
- Use session/window listing and pane capture to monitor status and errors