Tmux Command Cheatsheet

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Tmux Command Cheatsheet

Tmux Command Cheatsheet summarizes session, window, and pane operations in the tmux terminal multiplexer. Sessions group terminal work, windows contain layouts, and panes divide a window into separate terminal views. Understanding these levels helps target navigation or management commands without accidentally closing the wrong shell or process. A cheatsheet works best as a memory aid while you practice a concrete task. Read the command or syntax together with its arguments, placeholders, and surrounding context. Similar-looking options can have very different meanings, and an example written for one platform or version may need adjustment elsewhere. Keep the reference beside a small test case, use read-only examples first when possible, and check the relevant help output before applying an unfamiliar command to valuable files or a running service.

Guide updated October 13, 2026

How to use this tool

1. Identify the operation you want to perform and find the matching section of the reference. Read the whole example before copying any part of it.
2. Inspect available sessions, identify the intended target, and practice navigation in a test session before changing important work.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Try the adapted example on a small test case, compare the result with the explanation, and save the command with a note about the context in which it works.

SEE IT IN PRACTICE

A worked example

tmux ls

A listing of tmux sessions

The session names and status information help choose the correct attachment target instead of relying on whichever session is current.

Sessions, windows, and panes are different targets

A session contains windows, and a window can be split into panes. A navigation command changes the active view, while a kill command changes the lifecycle of the target and its processes. Identify the level you intend to affect before using a shortcut from the reference. Listing sessions and using meaningful names helps when returning to older work. A pane's visible command prompt is useful context, but it does not necessarily reveal every background process associated with the session.

Prefix bindings can be customized

The familiar default prefix is only a default; a user's configuration can remap it and many subsequent keys. If a shortcut fails, inspect the configuration rather than assuming the session is unresponsive. Detaching leaves the session available for later attachment, while exiting the last shell can end it. Practice layout and navigation changes in a test session before applying them to important work. Persistent terminals are convenient, but application state and data still need their own monitoring and preservation.

When this tool is useful

• Find a tmux navigation shortcut
• Understand session and pane structure
• Manage a persistent development terminal

Tips for a better result

• Confirm the target session, window, or pane and distinguish navigation from termination commands before applying an example.
• Replace example paths, identifiers, and names deliberately. Copying a reference command unchanged can target a different file, branch, service, or environment from the one you intended.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions