archive/tmux/home/dot_claude/exact_skills/tmux/SKILL.md
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".
npx skillsauth add jasonkuhrt/dotfiles tmuxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Terminal multiplexer - persistent sessions with splits and windows.
Local docs: This skill maintains a searchable copy of
man tmuxat./man-pages/. Ref MCP doesn't index man pages, so grep these files when you need tmux syntax (options, commands, formats, styles, hooks). See reference/man-pages.md.Releases: Track tmux updates at https://github.com/tmux/tmux/releases
tmux server (background daemon)
├── Session: project-a
│ ├── Window 0 (tab)
│ │ ├── Pane 0 → shell process (own cwd, env, history)
│ │ └── Pane 1 → shell process (own cwd, env, history)
│ └── Window 1 (tab)
│ └── Pane 0 → shell process
└── Session: project-b
└── Window 0
└── Pane 0 → shell process
Each pane is a fully independent shell with its own working directory, environment variables, and running processes. Switching panes/windows just changes which shell you're viewing.
Creating a session (tmux new-session):
Attaching to a session (tmux attach):
tmux attach is completely irrelevantThis is why you can tt from anywhere and land in the same session state - attaching is just connecting a display to existing processes.
| User Need | Use | |-----------|-----| | Real-time visibility of logs (dev server, build output) | tmux pane | | Might interact with process | tmux pane | | Just need to know when done / final result | CC background process |
Default: Dev servers and processes that emit logs user is developing against → tmux pane.
tmux list-panestmux capture-pane -t :.1 -p -S -50 # last 50 lines from pane 1
See sending-commands reference for target format syntax (-t session:window.pane).
See sending-commands reference for:
Use tt (tmux toggle) to attach/create session named after current directory:
cd ~/projects/myapp && tt # → Session: myapp
cd ~/projects/dotfiles && tt # → Session: dotfiles
The t abbreviation expands to tmux for direct commands: t list-sessions, t list-panes, etc.
| Task | Command |
| ----------------- | ------------------------------------- |
| Toggle session | tt |
| List sessions | t list-sessions |
| List panes | t list-panes |
| Capture pane | t capture-pane -t :.N -p -S -100 |
| Split vertical | t split-window -h |
| Send command | t send-keys -t :.N "cmd" Enter |
| New session | t new -s name |
| Kill session | t kill-session -t name |
| Reload config | t source-file ~/.config/tmux/tmux.conf |
Reload caveat:
terminal-overrideschanges only affect new panes/windows. If testing terminal settings, create a new pane after reload.
Sessions accumulate. Periodically clean up:
t list-sessions # see all sessions
t kill-session -t old-proj # kill one
t kill-server # nuclear option
man tmuxPlugins (in use):
prefix + f)prefix + u)See landscape.md for plugins to revisit.
Integrations:
development
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".
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.