tmux
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
Use left/top coordinates to resolve spatial references within the current window (LHS = lowest left, RHS = highest left, top = lowest top, bottom = highest top). When describing layouts, draw ASCII box diagrams showing pane positions and sizes.
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, which is usually enough to identify a window without capturing its content. Windows marked here are the current window; bell or activity flags mean the window needs attention (a process finished, errored, or produced output).
Sessions
!bash ${CLAUDE_SKILL_DIR}/scripts/sessions.sh
Drilling Into Other Targets
Each script accepts an optional target argument so you can inspect any pane, window, or session — not just the current one:
bash ${CLAUDE_SKILL_DIR}/scripts/session.sh other-session
bash ${CLAUDE_SKILL_DIR}/scripts/window.sh other-session:2
bash ${CLAUDE_SKILL_DIR}/scripts/pane.sh %12
Compose them to drill down: pick a session from sessions.sh, list its windows with session.sh <name>, then inspect a specific window with window.sh <name>:<idx>.
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.
Layout Mapping
| User intent | Flags | Notes |
|---|---|---|
| right / beside | -h -d |
Horizontal split |
| below / underneath | -v -d |
Vertical split |
| right sidebar | -h -d -l 40% |
Narrow right pane |
| left sidebar | -h -d -b -l 40% |
Narrow left pane (-b = before) |
| bottom panel | -v -d -l 25% |
Short pane below |
| top panel | -v -d -b -l 25% |
Short pane above |
Running a Command
tmux split-window -h -d -t $TMUX_PANE 'tail -f logs/dev.log'
The command string runs in the new pane's shell. When it exits, the pane closes. Use $SHELL or omit the command to open an interactive shell.
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"'
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 can see changes in real-time as you edit.
tmux split-window -h -d -l 40% -t $TMUX_PANE '<command> <file>'
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 -p to print to stdout instead of a paste buffer:
tmux capture-pane -t $TARGET -p
tmux capture-pane -t $TARGET -p -S -100
-S -100 includes 100 lines of scrollback above the visible area.
Gotchas
- Always use
-P -F '#{pane_id}'to capture pane IDs at creation time - Always use
-donsplit-windowto avoid switching Claude's pane - Use
$TMUX_PANE(set by tmux natively and injected by context hook) to target the current pane