tmux Plugin Manager TPM: Install and Manage Plugins (2026)

TPM (tmux Plugin Manager) lets you easily install and manage plugins for tmux, turning your terminal multiplexer into a powerful, customizable IDE.

Here’s TPM in action:

Imagine you have a ~/.tmux.conf file. With TPM, it looks like this:

# ~/.tmux.conf

# Set prefix key to Ctrl+a
set -g prefix C-a
unbind C-b
bind C-a send-prefix

# TPM plugins
set -g @plugin 'tmux-plugins/tpm'
set -g @plugin 'tmux-plugins/tmux-sensible'
set -g @plugin 'christoomey/vim-tmux-navigator'
set -g @plugin 'tmux-plugins/tmux-resurrect'
set -g @plugin 'tmux-plugins/tmux-continuum'

# Optional: tmux-resurrect configuration
set -g @resurrect-capture-pane-contents 'on'
set -g @resurrect-strategy-nvim 'session'

# Initialize TPM (keep this line at the bottom of tmux.conf)
run '~/.tmux-plugins/tpm/tpm'

When you open a new tmux session or reload your config (Ctrl+a then :source-file ~/.tmux.conf), TPM kicks in. It reads the lines starting with @plugin, fetches the specified plugins from their GitHub repositories, and makes them available.

Let’s break down how this works and what you control.

The Problem TPM Solves

Before TPM, managing tmux plugins was a manual, tedious process. You’d have to:

1. Find a plugin on GitHub.
2. Manually clone its repository into a specific directory (e.g., ~/.tmux/plugins/).
3. Manually configure your ~/.tmux.conf to load the plugin’s scripts.
4. Repeat for every plugin.
5. Manually update each plugin by pulling changes from its Git repository.

This was cumbersome, error-prone, and made it hard to share your tmux setup. TPM automates all of this.

How TPM Works Internally

1. Initialization: When run '~/.tmux-plugins/tpm/tpm' is executed, TPM itself is loaded.
2. Plugin Discovery: TPM scans your ~/.tmux.conf for lines starting with set -g @plugin 'owner/repo'.
3. Cloning/Updating:
   • If a plugin’s directory (e.g., ~/.tmux-plugins/plugins/tmux-plugins/tmux-sensible) doesn’t exist, TPM clones it from GitHub.
   • If the directory exists, TPM checks for updates and pulls the latest changes from the remote repository.
4. Loading: After ensuring all plugins are present and up-to-date, TPM sources the necessary plugin scripts (usually files named plugin.tmux or similar within the plugin’s directory) into your current tmux session. This makes the plugin’s commands and keybindings available.
5. Management Commands: TPM provides commands like run '~/.tmux-plugins/tpm/tpm' install-plugins to explicitly trigger plugin installation and updates.

Key Levers You Control

• set -g @plugin 'owner/repo': This is the core. owner/repo refers to the GitHub username/organization and the repository name of the tmux plugin. TPM uses this to find and manage the plugin.
• run '~/.tmux-plugins/tpm/tpm': This line must be at the end of your ~/.tmux.conf. It tells tmux to execute the TPM script, which in turn handles plugin discovery, cloning, and loading.
• Plugin-Specific Options: Many plugins offer configuration options that you set in ~/.tmux.conf using variables prefixed with @plugin-. For example, @resurrect-capture-pane-contents 'on' configures the tmux-resurrect plugin.
• TPM Commands: You can manually trigger TPM actions from within tmux by pressing your prefix key, then typing :run '~/.tmux-plugins/tpm/tpm' install-plugins. This forces TPM to check for and install/update all listed plugins.

The One Thing Most People Don’t Realize

While TPM handles cloning and updating, it doesn’t automatically apply new configurations or commands introduced by a plugin update. After TPM updates a plugin (either on startup or via install-plugins), you still need to reload your ~/.tmux.conf for those changes to take effect. This is typically done by pressing your prefix key, then typing :source-file ~/.tmux.conf. Many users expect plugin updates to be seamlessly active immediately, but the tmux server needs to re-read its configuration.

This mechanism ensures that your tmux environment can be precisely tailored to your workflow, from simple enhancements to complex session management and pane navigation.

The next step is understanding how to define custom keybindings that leverage the newly installed plugin commands.