| name | tmux |
| description | Tmux session, window, and pane management. Use when capturing output, sending keys, opening processes in panes, or checking notifications. |
| argument-hint | [capture | send | split | notify | list] [target ...] |
| effort | low |
| allowed-tools | ["Bash(bash ${CLAUDE_SKILL_DIR}/scripts/pane.sh:*)","Bash(bash ${CLAUDE_SKILL_DIR}/scripts/window.sh:*)","Bash(bash ${CLAUDE_SKILL_DIR}/scripts/session.sh:*)","Bash(bash ${CLAUDE_SKILL_DIR}/scripts/sessions.sh)"] |
| hooks | {"PreToolUse":[{"matcher":"Bash(tmux:*)","hooks":"[Truncated]"},{"matcher":"Bash(bash ${CLAUDE_SKILL_DIR}/scripts/:*)","hooks":"[Truncated]"}]} |
Tmux
Arguments
$0 (optional verb) routes to a section, with the target pane, window, or session as the rest: capture to Capturing Pane Content, send to Starting Claude Sessions, split to Opening Panes, notify (which windows need attention) to Session, list to Drilling Into Other Targets.
Pane
!bash ${CLAUDE_SKILL_DIR}/scripts/pane.sh
Use $TMUX_PANE to identify the current pane and target adjacent ones.
Window
!bash ${CLAUDE_SKILL_DIR}/scripts/window.sh
Each pane line ends with its geometry as @<left>,<top> <width>x<height>, in cell coordinates from the window's top-left. When describing layouts, draw ASCII box diagrams from the positions and sizes.
Worktrees and Parallel Panes
Panes in a git repo show their branch and whether the checkout is a linked (worktree) or the primary (main) one. When the user refers to work by branch or worktree, match the reference to a pane and dispatch to it with send-keys rather than entering a worktree of your own. A pane already in a worktree is set up for parallel work. Hand off to it instead of duplicating the checkout.
Session
!bash ${CLAUDE_SKILL_DIR}/scripts/session.sh
The TITLE column shows the active pane's title in each window. Claude sessions advertise their current task there, usually enough to identify a window without capturing its content. bell or activity flags mean the window needs attention.
Sessions
!bash ${CLAUDE_SKILL_DIR}/scripts/sessions.sh
Drilling Into Other Targets
Each script accepts an optional target argument to inspect any pane, window, or session, not just the current one: a session name for session.sh, name:index for window.sh, %id for pane.sh. Compose them to drill down from session to window to pane.
Opening Panes
Use split-window with -t $TMUX_PANE so new panes open relative to Claude's pane. Always pass -d to avoid switching Claude's own pane to the new one, and -P -F '#{pane_id}' to capture the new pane's ID at creation time. Sidebars are -h splits at -l 40%, top/bottom panels -v at -l 25%, and -b places the new pane before the current one (left or top).
Running a Command
Inline a command string only for a single bare command:
tmux split-window -h -d -t $TMUX_PANE 'tail -f logs/dev.log'
The command runs in the new pane's shell. When it exits, the pane closes. Use $SHELL or omit the command to open an interactive shell.
Anything past a bare command can make split-window silently fail: a ;, quotes, an exec fallback, or other shell metacharacters. The failure is quiet: no pane opens, no error prints, and -P -F '#{pane_id}' returns nothing. Split bare and send-keys the command instead. The new pane's shell runs the keys verbatim, past tmux's own parsing of the inline string:
pane=$(tmux split-window -h -d -t $TMUX_PANE -P -F '#{pane_id}')
tmux send-keys -t "$pane" 'cd repo; exec zsh' Enter
Starting Claude Sessions
Pass the initial prompt as a CLI argument rather than using send-keys:
tmux split-window -h -d -t $TMUX_PANE 'claude "analyze the test failures"'
A prompt with metacharacters hits the silent inline-parsing failure (see Running a Command). Split bare and send-keys the whole claude '...' line. Use send-keys only for follow-up messages to an already-running session.
Collaborative File Viewing
When collaborating on a file, open it in a sidebar pane so the user sees changes in real-time as you edit.
tmux split-window -h -d -l 40% -t $TMUX_PANE '<command> <file>'
Inline is safe only when both the command and the path are bare. A filename with a space, or a $EDITOR carrying flags (code -w), hits the silent no-op (see Running a Command).
Available Tools
!bash ${CLAUDE_SKILL_DIR}/scripts/tools.sh
Markdown Files
Prefer a terminal markdown renderer with file watching. Tools in preference order:
| Tool | Command | Notes |
|---|
| bun | bun --watch file.md | Rendered markdown with live reload |
| glow | glow -w 0 file.md | Rendered, no watch (reopen on change) |
| batwatch | batwatch --watcher poll file.md | Syntax-highlighted with file watching |
| bat | bat --paging always file.md | Syntax-highlighted source, no watch |
| less | less file.md | Plain text fallback |
Other Files
Open with $EDITOR when set, otherwise fall back to read-only viewers:
| Tool | Command | Notes |
|---|
$EDITOR | $EDITOR file.ts | User's preferred editor, most auto-reload on external changes |
| batwatch | batwatch --watcher poll file.ts | Syntax-highlighted with file watching |
| bat | bat --paging always file.ts | Syntax-highlighted, read-only |
| less | less file.ts | Plain text fallback |
Use the first available option. If the pane exits immediately, the tool is missing; try the next.
Capturing Pane Content
Use capture-pane -t <target> -p to print to stdout instead of a paste buffer, and -S -100 to include 100 lines of scrollback above the visible area.