---

name: tmux description: Use when managing terminal processes - starting dev servers, reading logs from other panes, sending commands to panes, or deciding between tmux pane vs CC background process. Triggers on "start server", "check logs", "run in background", "new pane", "dev server".

tmux

Terminal multiplexer - persistent sessions with splits and windows.

When to Use tmux Pane vs CC Background Process

Default: Dev servers and processes that emit logs user is developing against → tmux pane.

Reading Pane Output

1. Discover pane layout: tmux list-panes
2. Capture with appropriate depth:

   Copytmux capture-pane -t :.1 -p -S -50  # last 50 lines from pane 1
   

Target format: -t session:window.pane

• :.1 = current session, current window, pane 1
• :.2 = pane 2, etc.

Starting Processes in New Panes

See sending-commands reference for:

• Creating new panes and sending commands
• Starting dev servers
• send-keys patterns

Directory-Based Sessions

Use t command to attach/create session named after current directory:

Copycd ~/projects/myapp && t   # → Session: myapp
cd ~/projects/dotfiles && t # → Session: dotfiles

Creates new session if none exists, attaches if it does. Use this for starting work in a project.

Quick Reference

Maintenance

Sessions accumulate. Periodically clean up:

Copytmux ls                        # see all sessions
tmux kill-session -t old-proj  # kill one
tmux kill-server               # kill all

References

• Config - locations, tpm-redux, dotfiles setup
• Sending Commands - send-keys, new panes, starting servers
• Landscape - plugins, ecosystem, setup recommendations

Plugins:

• Resurrect - manual save/restore sessions
• Continuum - auto save/restore (extends resurrect)
• Sessionx - fuzzy session picker, worktree workflows

Integrations:

• Zed - auto-attach to project sessions
• Ghostty - manual attach workflows