tmux — Terminal Multiplexer for SysAdmins

📦 Installation

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf install tmux

Debian / Ubuntu

sudo apt install tmux

Verify

tmux -V
# tmux 3.3a  (or similar)

tmux is in every major distro's base repo. No EPEL, no PPA needed. If it is not already installed on your servers, it should be. Add it to your baseline package list.

Optional: Install a Recent Version from Source

Most distro packages are fine. If you need tmux 3.x features (better mouse support, extended keys) on an older RHEL system, you can build from source, but for most SysAdmin use the repo version is sufficient.

⌨️ Basic Usage

tmux has three levels: sessions, windows, and panes. A session contains windows. A window contains panes. You can have as many of each as you like.

SESSION: prod-maintenance ├── Window 0: logs │ ├── Pane 0: tail -f /var/log/messages │ └── Pane 1: journalctl -f -u httpd └── Window 1: shell └── Pane 0: bash prompt

The Prefix Key

Every tmux command starts with the prefix key, which is Ctrl+b by default. Press prefix, release it, then press the command key. You will see this written as C-b in tmux documentation.

Many experienced users remap the prefix to Ctrl+a (screen-style) in ~/.tmux.conf. Use whatever your fingers know. The default C-b works fine if you are starting fresh.

Essential Commands

Action	Command
Start a new named session	`tmux new -s mysession`
List sessions	`tmux ls`
Attach to a session	`tmux attach -t mysession`
Detach from session	C-b d
Kill a session	`tmux kill-session -t mysession`
Split pane horizontal	C-b %
Split pane vertical	C-b "
Move between panes	C-b arrow keys
New window	C-b c
Next window	C-b n
Previous window	C-b p
Rename window	C-b ,
Show key bindings	C-b ?
Enter copy mode (scroll)	C-b [

The Attach/Detach Cycle

This is the workflow that matters most:

# On your workstation — SSH in and start a named session
ssh admin@prod-server-01
tmux new -s maintenance

# Do your work inside tmux
# ...

# Something comes up, or your connection drops — detach cleanly
# C-b d

# Later — reconnect and pick up exactly where you left off
ssh admin@prod-server-01
tmux attach -t maintenance

Always name your sessions. tmux new -s descriptive-name makes tmux ls readable when you have multiple sessions running on a server.

🐧 SysAdmin Use Cases

Long-Running Jobs That Must Survive Disconnects

The original killer use case. Package upgrades, database dumps, disk checks, migrations — anything that takes minutes to hours and cannot be interrupted:

tmux new -s db-backup
pg_dump -Fc mydb > /backup/mydb-$(date +%Y%m%d).dump
# C-b d   (detach — job keeps running)

# Hours later:
tmux attach -t db-backup
# Session is still there, job completed, output is waiting

Multi-Pane Monitoring Dashboard

Split your window into panes and watch multiple streams simultaneously:

tmux new -s monitor
# Split horizontal: C-b %
# Split the right pane vertical: C-b "

# Pane 1: system logs
tail -f /var/log/messages

# Pane 2: service status
watch -n 5 systemctl status httpd mariadb

# Pane 3: active connections
watch -n 2 ss -tnp

Named Sessions Per Project or Server Role

Keep separate tmux sessions for separate contexts so you are never hunting for the right terminal window:

tmux new -s prod-web      # production web servers
tmux new -s prod-db       # database work
tmux new -s dev-testing   # development environment
tmux new -s log-watch     # persistent log monitoring

tmux ls
# prod-web: 2 windows (created Thu Mar 28 09:14:22 2026)
# prod-db: 1 window (created Thu Mar 28 09:20:01 2026)
# dev-testing: 3 windows (created Thu Mar 28 10:05:44 2026)
# log-watch: 1 window (created Thu Mar 28 07:00:12 2026)

Patch Night Workflow

Run updates across multiple servers in parallel without juggling terminal windows:

# Open one tmux session, create a window per server
tmux new -s patch-night
# Window 0: server01
ssh admin@server01
sudo dnf update -y

# C-b c   (new window)
# Window 1: server02
ssh admin@server02
sudo dnf update -y

# C-b c   (new window)
# Window 2: server03
ssh admin@server03
sudo dnf update -y

# Toggle between them with C-b n / C-b p
# Or jump directly: C-b 0, C-b 1, C-b 2

Shared Session for Collaborative Troubleshooting

Two admins can attach to the same tmux session and see each other's terminal in real time. Useful for training a junior admin or pair troubleshooting a production issue:

# Admin 1 creates session
tmux new -s collab

# Admin 2 attaches to same session (both see the same screen)
tmux attach -t collab

Both users must be on the same server with access to the same socket file. This is most practical when you are both already SSH'd into the same box. For remote pair work across different connections, look at tmate (tmux-compatible session sharing over the internet).

Persistent Log Watching

Start a dedicated session just for log tailing that you attach to whenever you need it:

tmux new -s logs
# Window 0: system
journalctl -f

# C-b c
# Window 1: httpd
tail -f /var/log/httpd/error_log

# C-b c
# Window 2: auth
tail -f /var/log/secure

# Detach — session lives on, logs keep scrolling
# C-b d

🤖 tmux + AI Tools

tmux is the natural container for AI-assisted SysAdmin workflows. The same session persistence and pane splitting that makes it useful for long jobs makes it ideal for running AI tools alongside your normal shell work.

AI Tool Pane Alongside Your Shell

Keep sgpt or an AI session running in a pane while you work in another:

tmux new -s ai-work
# Left pane: your shell
# C-b %   (split)
# Right pane: sgpt chat mode

sgpt --chat mywork "You are helping me troubleshoot a RHEL 9 httpd issue"
# Ask questions, get answers, switch back to left pane to apply them
# C-b <left arrow>

sgpt Log Analysis in a Dedicated Pane

# Pane 1: live log tail
tail -f /var/log/httpd/error_log | tee /tmp/current-errors.log

# Pane 2: on-demand AI analysis
cat /tmp/current-errors.log | sgpt "Summarize the recurring errors and suggest root causes"

aider in tmux — Long AI Coding Sessions

aider sessions can run for a long time as you work through a codebase. tmux gives you session persistence so a disconnect does not abort the work:

tmux new -s aider-work
cd /opt/myproject
aider --model gpt-4o myscript.sh

# Work through changes with aider
# Detach — aider session is preserved
# C-b d

# Reconnect later:
tmux attach -t aider-work

ollama in Its Own Session

Run ollama serve in a tmux session so it persists as a background service even if your shell session ends:

tmux new -s ollama-server
ollama serve
# C-b d   (detach — ollama keeps running)

# From any other pane or session:
sgpt --api-host http://localhost:11434 "explain this error"

fabric Pattern Pipeline Monitoring

# Pane 1: run a recurring fabric analysis
watch -n 300 'journalctl --since "5 minutes ago" | fabric -p analyze_logs'

# Pane 2: shell for responding to findings

The pattern of “AI tool in one pane, shell in another” is the tmux superpower for AI-assisted sysadmin work. You stop alt-tabbing between windows and start working in one coherent workspace.

⚙️ Configuration — ~/.tmux.conf

tmux is highly configurable. A minimal ~/.tmux.conf goes a long way. Here is a practical starting point for SysAdmins:

# ~/.tmux.conf — practical SysAdmin baseline

# Remap prefix to Ctrl+a (screen-style) — optional, remove if you prefer C-b
# unbind C-b
# set-option -g prefix C-a
# bind-key C-a send-prefix

# Increase scrollback buffer (default is 2000 — too small for log work)
set-option -g history-limit 50000

# Enable mouse support (click to select panes, drag to resize)
set -g mouse on

# Start window and pane numbering at 1 (easier keyboard access)
set -g base-index 1
setw -g pane-base-index 1

# Re-number windows when one is closed
set -g renumber-windows on

# Status bar — show session name, window list, date/time
set -g status-right '%Y-%m-%d %H:%M '
set -g status-bg colour235
set -g status-fg colour136

# Reload config without restarting tmux
bind r source-file ~/.tmux.conf \; display "Config reloaded"

# Intuitive pane splitting (| and - instead of % and ")
bind | split-window -h
bind - split-window -v
unbind '"'
unbind %

# Pane navigation with Alt+arrow (no prefix needed)
bind -n M-Left  select-pane -L
bind -n M-Right select-pane -R
bind -n M-Up    select-pane -U
bind -n M-Down  select-pane -D

After editing ~/.tmux.conf, reload it with C-b r (if you added the reload bind above) or from the shell with tmux source-file ~/.tmux.conf.

Key Config Options Reference

Option	What it does
`history-limit 50000`	Scrollback buffer size — increase for log-heavy work
`mouse on`	Click panes to focus, drag borders to resize
`base-index 1`	Windows numbered from 1 — easier to reach on keyboard
`renumber-windows on`	Keeps window numbers contiguous after closing one
`status-right`	Right side of status bar — add date, time, hostname

📊 Honest Assessment

The Good

Session persistence is genuinely essential. Once you have lost a long-running job to a dropped SSH connection and then discovered tmux, you never go back. It solves a real, recurring SysAdmin pain point.
Zero ongoing cost. No API key. No subscription. No cloud dependency. It is in every distro's base repo and it works the same way on every Linux server you will ever touch.
Muscle memory compounds. The keybindings feel awkward for the first week and then become completely automatic. The investment pays off quickly.
AI tools are better inside tmux. Session persistence, pane splitting, and the ability to detach and reattach make tmux the ideal wrapper for any AI tool that runs interactively at the terminal.

The Friction

The prefix key is a habit change. The C-b prefix takes getting used to, especially if you already have screen habits. Give yourself two weeks before judging it.
Copy/paste is not obvious. Copying text from a tmux pane to your local clipboard works differently depending on your terminal emulator and OS. Mouse mode helps. Expect to look this up once.
Config rabbit hole is real. There are entire dotfile repositories dedicated to elaborate tmux configs. Resist the urge. The minimal config above is sufficient for SysAdmin work. You can always add more later.
Not a replacement for a terminal emulator's tabs. On your local workstation you may prefer your terminal app's native tabs. tmux's value multiplies on remote servers where you only have one SSH connection to work with.

Bottom Line

tmux belongs in your baseline install on every server you manage. It is not an AI tool — it is the infrastructure that makes your AI tools (and everything else you do over SSH) more reliable. The learning curve is real but short. The payoff is permanent.

If you manage remote Linux servers and you are not using tmux, you are working harder than you need to.

🔗 Related Tools in This Section

Shell GPT (sgpt) — run AI queries in one pane while you work in another
ollama — keep ollama serve running in a dedicated tmux session
aider — long AI coding sessions benefit from tmux session persistence
fabric — run fabric pipelines in a pane alongside your shell
fzf — browse tmux session and window lists interactively with fzf

🖥️ tmux

What Is tmux?

📦 Installation

RHEL / CentOS / Rocky / AlmaLinux

Debian / Ubuntu

Verify

Optional: Install a Recent Version from Source

⌨️ Basic Usage

The Prefix Key

Essential Commands

The Attach/Detach Cycle

🐧 SysAdmin Use Cases

Long-Running Jobs That Must Survive Disconnects

Multi-Pane Monitoring Dashboard

Named Sessions Per Project or Server Role

Patch Night Workflow

Shared Session for Collaborative Troubleshooting

Persistent Log Watching

🤖 tmux + AI Tools

AI Tool Pane Alongside Your Shell

sgpt Log Analysis in a Dedicated Pane

aider in tmux — Long AI Coding Sessions

ollama in Its Own Session

fabric Pattern Pipeline Monitoring

⚙️ Configuration — ~/.tmux.conf

Key Config Options Reference

📊 Honest Assessment

The Good

The Friction

Bottom Line

🔗 Related Tools in This Section