tmux

name	tmux
description	Manage concurrent processes using tmux. Use when running servers, long tasks, or orchestrating multiple agents in separate panes. Essential for sending multi-line text or instructions to other tmux panes safely.
allowed-tools	["Bash"]

Tmux Skill

This skill empowers you to manage multiple concurrent processes (like servers, watchers, or long builds) using tmux directly from the Bash tool.

Since you are likely already running inside a tmux session, you can spawn new windows or panes to handle these tasks without blocking your main communication channel.

1. Verify Environment & Check Status

First, verify you are running inside tmux:

echo $TMUX

If this returns empty, you are not running inside tmux. Use explicit tmux targets such as session:window.pane with the helper scripts.

Once verified, check your current windows:

tmux list-windows

If you are outside tmux but need to operate on an existing session, use the helper scripts with explicit tmux targets:

tmux list-sessions
tmux list-windows -t "session-name"
pane=$(launch-agent -a codex -t "session-name:window-name" -d /repo -- exec --help)
send-to-pane -t "session-name:window-name.pane" /tmp/prompt.txt
poll-agents -t "$pane"

Before launching an interactive agent or other long-running CLI in a pane, check the installed CLI's --help output for the exact flags supported on that machine. Agent CLI flags change over time, and a rejected flag can leave the pane in a failed or idle state.

2. Spawn a Background Process

To run a command (e.g., a dev server) in a way that persists and can be inspected:

1. Create a new detached window with a specific name. This keeps it isolated and easy to reference.

   tmux new-window -n "server-log" -d
   

   (Replace "server-log" with a relevant name for your task)

2. Send the command to that window.

   tmux send-keys -t "server-log" "npm start" C-m
   

   (C-m simulates the Enter key)

3. Sending Text to Panes

Warning: send-keys interprets control sequences. Multi-line text or text with special characters can trigger tmux modes (like C-r for search). Use the right method:

Content Type	Method
Simple shell command	send-keys "cmd" C-m
Single line, may have special chars	send-keys -l "text" then send-keys C-m
Multi-line text or instructions	send-to-pane -t <target> <file>

Literal mode (-l flag) prevents interpreting escape sequences:

tmux send-keys -l -t "target" "text with C-r and other chars"
tmux send-keys -t "target" C-m

Multi-line content — use send-to-pane, which wraps load-buffer safely:

cat > /tmp/msg.txt << 'EOF'
Your multi-line content here.
Can include any characters safely.
EOF
send-to-pane -t "target" /tmp/msg.txt

4. Interacting with Other Agents

When sending instructions to another Claude instance running in a tmux pane:

cat > /tmp/instructions.txt << 'EOF'
Fix the authentication bug in src/auth.ts:
1. The token validation is missing null checks
2. Add proper error handling for expired tokens
EOF
send-to-pane -t %31 /tmp/instructions.txt

Never use send-keys directly for prompts or instructions — the text will likely contain characters that trigger tmux modes.

5. Helper Scripts

For orchestration workflows, prefer these scripts over raw tmux commands:

Task	Script	Example
Send text to pane	send-to-pane	echo "cmd" | send-to-pane -t %31
Send file to pane	send-to-pane	send-to-pane -t atlas:review.1 /tmp/prompt.txt
Launch agent pane	launch-agent	pane=$(launch-agent -a codex -t atlas:review -d /path)
Monitor panes	poll-agents	poll-agents -p -t %31 -t atlas:review.2

These wrap the tmux boilerplate (temp files, load-buffer, paste-buffer) into single commands. Run any script with --help for full usage.

Prefer tmux-native targets (%31, atlas:review, atlas:review.2) over separate session/window flags. The raw tmux commands in the sections below remain useful for understanding what the scripts do and for ad-hoc operations.

When using poll-agents, choose a completion sentinel that does not appear literally in the command line or prompt visible in pane scrollback. For example, ask the agent to output "the words PHASE and COMPLETE separated by one space" instead of embedding PHASE COMPLETE directly in the prompt.

6. Inspect Output (Read Logs)

You can read the output of that pane at any time without switching your context.

Get the current visible screen:

tmux capture-pane -p -t "server-log"

Get the entire history (scrollback):

tmux capture-pane -p -S - -t "server-log"

Use this if the output might have scrolled off the screen.

7. Interact with the Process

If you need to stop or restart the process:

Send Ctrl+C (Interrupt):

tmux send-keys -t "server-log" C-c

Kill the window (Clean up):

tmux kill-window -t "server-log"

8. Advanced: Chaining Commands

You can chain multiple tmux commands in a single invocation using ';' (note the quotes to avoid interpretation by the shell). This is faster and cleaner than running multiple tmux commands.

Example: Create window and start process in one go:

tmux new-window -n "server-log" -d ';' send-keys -t "server-log" "npm start" C-m

Quick Reference

Task	Command
Create window	tmux new-window -n "ID" -d
Run command	tmux send-keys -t "ID" "cmd" C-m
Send literal text	tmux send-keys -l -t "ID" "text"
Send multi-line	send-to-pane -t "ID" file
Read output	tmux capture-pane -p -t "ID"
Interrupt	tmux send-keys -t "ID" C-c
Kill window	tmux kill-window -t "ID"
Send to pane	echo "text" | send-to-pane -t %ID
Launch agent	pane=$(launch-agent -a codex -t atlas:review -d /path)
Poll agents	poll-agents -p -t %ID1 -t %ID2