agentleFS
Sign inStart free
bntvllntbntvllnt/agent-skills/tmux/SKILL.md

tmux

Skill16 starsChanged 8 months agoMITView on GitHub

Complete tmux terminal multiplexer management: sessions, windows, panes, layouts, scripting, and configuration. Auto-activates on: "tmux", "session", "window", "pane", "split", "attach", "detach", "multiplexer".

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, session-logs and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • seedprodSkill

    session-logs

    Search and analyze your own session logs (older/parent conversations) using jq.

    Also in 20 projects that use this

  • seedprodSkill

    voice-call

    Start voice calls via the OpenClaw voice-call plugin.

    Also in 18 projects that use this

  • AtomicBot-aiSkill

    taskflow

    Also in 7 projects that use this

  • jiulingyunSkill

    BlueBubbles

    为Clawdbot构建或更新BlueBubbles外部通道插件（扩展包，REST发送/探测，webhook入站）。

    Also in 16 projects that use this

  • hkyutongSkill

    openclaw-release-maintainer

    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.

    Also in 4 projects that use this

  • +5 more from seedprod

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 64 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Confirm before kill: Always confirm before kill-session, kill-window, kill-pane

    line 141
  2. Distinctive:

    Check attachments: Before killing, check if session has active clients

    line 142
  3. Very specific:

    Config backup: Before editing ~/.tmux.conf, suggest backup

    line 144
  4. Very specific:

    Check if inside tmux: [ -n "$TMUX" ]

    line 166

“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

tmux

Complete tmux management for terminal multiplexing.

Core Concepts

┌─────────────────────────────────────────────────────────────┐
│ SERVER (one per socket)                                     │
│  ┌───────────────────────────────────────────────────────┐  │
│  │ SESSION ($0, $1, ...)                                 │  │
│  │  ┌─────────────────┐  ┌─────────────────┐            │  │
│  │  │ WINDOW (@0)     │  │ WINDOW (@1)     │  ...       │  │
│  │  │  ┌────┬────┐   │  │  ┌────────────┐ │            │  │
│  │  │  │PANE│PANE│   │  │  │   PANE     │ │            │  │
│  │  │  │ %0 │ %1 │   │  │  │    %2      │ │            │  │
│  │  │  └────┴────┘   │  │  └────────────┘ │            │  │
│  │  └─────────────────┘  └─────────────────┘            │  │
│  └───────────────────────────────────────────────────────┘  │
└─────────────────────────────────────────────────────────────┘
  • Server: Background process managing all state
  • Session ($id): Named container of windows, persists after detach
  • Window (@id): Tab-like container of panes within a session
  • Pane (%id): Individual terminal within a window
  • Client: Terminal attached to a session

Router

User saysLoad referenceDo
list sessions / statusreferences/session-management.mdinspect sessions
new session / create sessionreferences/session-management.mdcreate session
attach / detachreferences/session-management.mdattach/detach
kill sessionreferences/session-management.mdterminate session
new window / create windowreferences/window-management.mdcreate window
rename windowreferences/window-management.mdrename window
kill window / close windowreferences/window-management.mdclose window
switch windowreferences/window-management.mdnavigate windows
split / new panereferences/pane-management.mdsplit pane
resize panereferences/pane-management.mdresize pane
move pane / swap panereferences/pane-management.mdrearrange panes
kill pane / close panereferences/pane-management.mdclose pane
layoutreferences/layouts.mdapply/manage layouts
copy / paste / bufferreferences/copy-mode.mdcopy mode operations
config / tmux.conf / settingsreferences/configuration.mdconfigure tmux
keybind / bind / unbindreferences/keybindings.mdkey bindings
script / automate / send-keysreferences/scripting.mdscripting/automation
capture / log / outputreferences/scripting.mdcapture pane content
help / keys / cheatsheetinlineshow key reference

Default Key Bindings (Prefix: C-b)

Session

KeyAction
dDetach from session
sList/switch sessions
$Rename session
( / )Previous/next session

Window

KeyAction
cCreate window
&Kill window (confirm)
,Rename window
0-9Switch to window N
n / pNext/previous window
lLast window
wList windows
fFind window

Pane

KeyAction
%Split horizontally (left/right)
"Split vertically (top/bottom)
xKill pane (confirm)
oCycle panes
qShow pane numbers
zToggle zoom
{ / }Swap pane left/right
!Break pane to window
ArrowsNavigate panes
SpaceCycle layouts
C-oRotate panes

Copy Mode

KeyAction
[Enter copy mode
]Paste buffer
=Choose paste buffer
#List buffers

Quick Reference

# Session
tmux new -s name              # Create named session
tmux attach -t name           # Attach to session
tmux ls                       # List sessions
tmux kill-session -t name     # Kill session

# Window
tmux new-window -n name       # Create named window
tmux select-window -t :N      # Go to window N
tmux rename-window name       # Rename current window

# Pane
tmux split-window -h          # Split horizontal
tmux split-window -v          # Split vertical
tmux select-pane -t :.N       # Go to pane N
tmux resize-pane -D 5         # Resize down 5 lines

# Info
tmux list-keys                # All key bindings
tmux info                     # Server info

Safety Rules

  • Confirm before kill: Always confirm before kill-session, kill-window, kill-pane
  • Check attachments: Before killing, check if session has active clients
  • Preserve work: Warn if panes have running processes
  • Config backup: Before editing ~/.tmux.conf, suggest backup

Confirmation Policy

Read-only (always OK):

  • tmux ls, list-sessions, list-windows, list-panes
  • tmux info, show-options, display-message
  • tmux list-keys, list-buffers

Requires confirmation:

  • kill-session, kill-window, kill-pane
  • kill-server
  • Editing ~/.tmux.conf
  • send-keys to panes (can affect running processes)

Environment Variables

VariableDescription
TMUXSocket path (set inside tmux)
TMUX_PANECurrent pane ID

Check if inside tmux: [ -n "$TMUX" ]

Troubleshooting

IssueSolution
"no server running"Start with tmux or tmux new
"sessions should be nested"Unset $TMUX or use tmux -u
Detached session lostCheck tmux ls, attach with tmux attach
Colors not workingSet TERM=xterm-256color or set -g default-terminal "tmux-256color"
Mouse not workingset -g mouse on in config

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free