Introduction<\/h2>\n\n\n\n

Tmux is a terminal multiplexer. It allows you to run and manage several command prompts simultaneously from one tmux session.<\/p>\n\n\n\n

Tmux uses a client\/server model, which allows it to persist connections. You can start a session from one computer, run several programs running in it, and then disconnect. You can later reconnect to the same session from a different computer and the same programs will be running.<\/p>\n\n\n\n

Install tmux on Debian and Ubuntu<\/h2>\n\n\n\n

On Debian and Ubuntu systems, install tmux with apt.<\/p>\n\n\n\n

$ sudo apt-get update && sudo apt-get -y install tmux\n<\/code><\/pre>\n\n\n\n
Install tmux on Redhat, CentOS, and Other RHEL-Based Distributions<\/h2>\n\n\n\n
On Redhat, CentOS, and other RHEL-based systems, install tmux with yum.<\/p>\n\n\n\n
$ sudo yum install update && sudo yum -y install tmux\n<\/code><\/pre>\n\n\n\n
Terminology<\/h2>\n\n\n\n
\n
Pane<\/strong> – A pane is simply a terminal prompt.<\/li>\n\n\n\n
Window<\/strong> – A window holds multiple panes (terminals) on one screen.<\/li>\n\n\n\n
Session<\/strong> – A session has multiple windows.<\/li>\n\n\n\n
Server<\/strong> – A server holds multiple sessions. It runs in the background and ensures the persistence of the sessions.<\/li>\n<\/ul>\n\n\n\n
Start a New tmux Session<\/h2>\n\n\n\n
$ tmux new -s start\n<\/code><\/pre>\n\n\n\n
You will see a bar at the bottom of the screen with the session name tmux created, start<\/strong>, in brackets. This is because tmux automatically logs in with your user account when it creates new panes.<\/p>\n\n\n\n
Maneuvering in tmux<\/h2>\n\n\n\n
Once inside a tmux session, you use a prefix key to trigger commands to tell tmux what to do. The default prefix key is CTRL<\/kbd> + B<\/kbd>. For example, if you want to tell tmux to create a new pane by splitting your screen into two vertical sections, you first type CTRL<\/kbd> + B<\/kbd>, then %<\/kbd>.<\/p>\n\n\n\n
Create Multiple Panes<\/h2>\n\n\n\n
If you typed CTRL<\/kbd> + B<\/kbd>, then %<\/kbd> as shown above, then you have two panes on your screen.<\/p>\n\n\n\n
\n
Split the current pane into two horizontal sections by typing CTRL<\/kbd> + B<\/kbd>, then \"<\/kbd>.<\/li>\n\n\n\n
To cycle through all three panes, type CTRL<\/kbd> + B<\/kbd>, then O<\/kbd>.<\/li>\n<\/ul>\n\n\n\n
Switch Between Panes<\/h2>\n\n\n\n
To switch between different open panes, use the arrow keys with the prefix.<\/p>\n\n\n\n
\n
CTRL<\/kbd> + B<\/kbd>, then UP<\/kbd>: Go to the pane above the current pane.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then DOWN<\/kbd>: Go to the pane below the current pane.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then LEFT<\/kbd>: Go to the pane on the left of the current pane.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then RIGHT<\/kbd>: Go to the pane on the right of the current pane.<\/li>\n<\/ul>\n\n\n\n
Create Multiple Windows<\/h2>\n\n\n\n
\n
Create a new window in the start<\/strong> session. Type CTRL<\/kbd> + B<\/kbd>, then C<\/kbd> to open a new blank terminal.<\/li>\n\n\n\n
Split this terminal into two horizontal panes with CTRL<\/kbd> + B<\/kbd>, then \"<\/kbd>.<\/li>\n\n\n\n
Create a third window with CTRL<\/kbd> + B<\/kbd>, then C<\/kbd>.You will see a new blank terminal again.<\/li>\n\n\n\n
Issue the command tmux list-windows<\/code>, then press ENTER<\/kbd> to confirm that you have three windows opened.<\/li>\n\n\n\n
Use CTRL<\/kbd> + B<\/kbd>, then N<\/kbd> to cycle between the three windows created.<\/li>\n<\/ol>\n\n\n\n
Attach and Detach to\/from a Session<\/h2>\n\n\n\n
\n
Use CTRL<\/kbd> + B<\/kbd>, then D<\/kbd> to detach from your current session.<\/li>\n\n\n\n
Reconnect to your session with tmux attach -t YOUR_SESSION_NAME<\/code>.<\/li>\n\n\n\n
Use CTRL<\/kbd> + B<\/kbd>, then N<\/kbd> to cycle between the windows in your session.<\/li>\n<\/ul>\n\n\n\n
Common Key Bindings<\/h2>\n\n\n\n
\n
CTRL<\/kbd> + B<\/kbd>, then C<\/kbd> : Create new window.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then ,<\/kbd> : Rename a window.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then N<\/kbd> : Move to the next window.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then P<\/kbd> : Move to the previous window.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then &<\/kbd> : Kill current window.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then %<\/kbd> : Split current pane into two (vertically).<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then \"<\/kbd> : Split current pane into two (horizontally).<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then O<\/kbd> : Switch to next pane.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then Q<\/kbd> : Show pane numbers (then type a # to switch to it).<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then D<\/kbd> : Detach from current session.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then ?<\/kbd> : List all key bindings.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then X<\/kbd>: Kill the active pane (after pressing Y<\/kbd> to confirm).<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then W<\/kbd>: Show an overview of all active windows and panes. Use the arrow keys to move through the list of windows and see a preview of the selected window. Press ENTER<\/kbd> to switch to the selected window. Press ESC<\/kbd> to exit the overview.<\/li>\n<\/ul>\n\n\n\n
Common Commands<\/h3>\n\n\n\n
\n
tmux list-sessions<\/code> – List existing tmux sessions.<\/li>\n\n\n\n
tmux new -s session-name<\/code> – Create a new tmux session named session-name.<\/li>\n\n\n\n
tmux attach -t session-name<\/code> – Connect to an existing tmux session named session-name.<\/li>\n\n\n\n
tmux switch -t session-name<\/code> – Switches to an existing tmux session named session-name.<\/li>\n<\/ul>\n\n\n\n
Use Vim Key Bindings to Switch Between Panes<\/h3>\n\n\n\n
Instead of using the arrow keys to switch between different panes, you can use the Vim keys H<\/kbd>, J<\/kbd>, K<\/kbd>, L<\/kbd>. To do this, update the tmux configuration file ~\/.tmux.conf<\/code>. If this file doesn’t exist, create it.<\/p>\n\n\n\n
Add these lines (the first line is a comment) to the configuration file to enable pane navigation using Vim keys:<\/p>\n\n\n\n
# hjkl pane traversal\n\nbind h select-pane -L\n\nbind j select-pane -D\n\nbind k select-pane -U\n\nbind l select-pane -R\n<\/code><\/pre>\n\n\n\n
After updating the configuration file, restart tmux. You can load the new configuration without restarting tmux by sourcing<\/em> the updated configuration file:<\/p>\n\n\n\n
tmux source-file ~\/.tmux.conf\n<\/code><\/pre>\n\n\n\n
The Meta Key<\/h2>\n\n\n\n
Many of the key bindings in the following sections are based on the Meta key. On most modern computers and keyboards, the Meta key is not one specific key. Depending on the system settings and the terminal emulator in use, the Meta key could be bound to either ESC<\/kbd>, ALT<\/kbd>, COMMAND<\/kbd>, WIN<\/kbd>, or Opt<\/code>. Where you see META<\/kbd> as part of a key binding, try using the ESC<\/kbd> key. If it doesn’t work, try one of the other keys mentioned above.<\/p>\n\n\n\n
Adjust Pane Size<\/h2>\n\n\n\n
When a window has multiple panes, you can change the size of individual panes.<\/p>\n\n\n\n
\n
To change the pane size, press and hold the prefix (CTRL<\/kbd> + B<\/kbd>), and simultaneously press one of the arrow keys.<\/li>\n\n\n\n
Hold down CTRL<\/kbd> + B<\/kbd>, and simultaneously press either UP<\/kbd> or DOWN<\/kbd>: Change the height of the pane.<\/li>\n\n\n\n
Hold down CTRL<\/kbd> + B<\/kbd>, and simultaneously press either LEFT<\/kbd> or RIGHT<\/kbd>: Change the width of the pane.<\/li>\n<\/ul>\n\n\n\n
The above key combinations resize the pane “continuously” as long as they are held pressed. To resize the pane one step at a time:<\/p>\n\n\n\n
\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + either UP<\/kbd> or DOWN<\/kbd>: Change the height of the pane.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + either LEFT<\/kbd> or RIGHT<\/kbd>: Change the width of the pane.<\/li>\n<\/ul>\n\n\n\n
Whether a particular key combination (above) increases or decreases the dimensions of the pane depends on the positioning of that pane relative to other panes.<\/p>\n\n\n\n
If the terminal emulator supports mouse use, you can resize panes by dragging their borders.<\/p>\n\n\n\n
Choose a Preset Pane Layout<\/h2>\n\n\n\n
Tmux has five different preset layouts for arranging multiple panes in a window:<\/p>\n\n\n\n
\n
All panes are stacked side-by-side.<\/li>\n\n\n\n
All panes are stacked on top of each other.<\/li>\n\n\n\n
The main pane takes up the entire screen width and the other panes are stacked side-by-side below it<\/li>\n\n\n\n
The main pane takes up the entire screen height and the others panes are stacked beside it on top of each other<\/li>\n\n\n\n
All panes are arranged in a grid.<\/li>\n<\/ol>\n\n\n\n
Start tmux and create 4 (or any number of) panes.<\/p>\n\n\n\n
To cycle through the different preset layouts use CTRL<\/kbd> + B<\/kbd>, then SPACE<\/kbd><\/p>\n\n\n\n
You can also choose a specific layout:<\/p>\n\n\n\n
\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + 1<\/kbd>: Switch to layout 1.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + 2<\/kbd>: Switch to layout 2.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + 3<\/kbd>: Switch to layout 3.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + 4<\/kbd>: Switch to layout 4.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + 5<\/kbd>: Switch to layout 5.<\/li>\n<\/ul>\n\n\n\n
Swapping Pane Positions<\/h2>\n\n\n\n
When a window has multiple panes, you can move the panes around and swap their positions.<\/p>\n\n\n\n
\n
Note: As described previously, CTRL<\/kbd> + B<\/kbd>, then O<\/kbd> cycles the cursor through the different panes. The above sequence is for cycling the positions of the panes themselves.<\/p>\n<\/blockquote>\n\n\n\n
\n
CTRL<\/kbd> + B<\/kbd>, then META<\/kbd> + O<\/kbd> cycles the positions of the panes clockwise.<\/li>\n\n\n\n
CTRL<\/kbd> + B<\/kbd>, then CTRL<\/kbd> + O<\/kbd> cycles the positions of the panes counterclockwise.<\/li>\n<\/ul>\n\n\n\n
Detach and Reattach Individual Panes<\/h2>\n\n\n\n
In a layout with multiple panes in a window, it is sometimes necessary to move a pane to a different location. Swapping pane positions (as described above) isn’t always sufficient, because it disturbs the positions of all the other panes. It is also sometimes necessary to move a pane to a different window in the same session.<\/p>\n\n\n\n
Use the command break-pane<\/code> in the tmux command prompt to detach a pane from the window. join-pane<\/code> reattaches the pane.<\/p>\n\n\n\n
To access the tmux command prompt, press the prefix CTRL<\/kbd> + B<\/kbd>, then press :<\/kbd>. This will open up a prompt at the bottom of the terminal. To exit it without entering any commands, press CTRL<\/kbd> + C<\/kbd>.<\/p>\n\n\n\n
To detach a pane, switch to the pane to be detached, activate the tmux command prompt (CTRL<\/kbd> + B<\/kbd>, then :<\/kbd>), and enter the command:<\/p>\n\n\n\n
break-pane -dP\n<\/code><\/pre>\n\n\n\n
This will detach the active pane and show its “ID”. This ID is of the format X:Y.Z<\/code> where X, Y, and Z are numbers. The previous pane becomes the new active pane. The ID is shown on top of the (new) active pane. Note down this ID and then dismiss it by pressing ESC<\/kbd>.<\/p>\n\n\n\n
The detached pane can be reattached next to any pane in any window in the same session. Switch to the pane next to which you want to reattach the detached pane. Activate the tmux command prompt and enter:<\/p>\n\n\n\n
join-pane -vs X:Y.Z\n<\/code><\/pre>\n\n\n\n
This reattaches the detached pane below the active pane (vs<\/code> stands for vertical split<\/em>). To reattach the detached pane on the right side of the active pane:<\/p>\n\n\n\n
join-pane -hs X:Y.Z\n<\/code><\/pre>\n\n\n\n
In the above command, hs<\/code> stands for horizontal split<\/em>.<\/p>\n\n\n\n
Share tmux Sessions Between Users<\/h2>\n\n\n\n
How Sessions Work<\/h3>\n\n\n\n
When you start tmux, it creates a new server instance and creates a session within that server.<\/p>\n\n\n\n
Tmux clients and servers are separate processes. They communicate via a UNIX socket. By default, tmux stores sockets in the \/tmp<\/code> directory. Sockets for servers created by an individual user are stored under a subdirectory named tmux-UID<\/code> where UID<\/code> is the UNIX UID of that user. A user whose UID<\/code> is 1001 will have its sockets stored in \/tmp\/tmux-1001<\/code>. The owner of this subdirectory is user1<\/code>. By default, no other user or group can access this subdirectory.<\/p>\n\n\n\n
Compatibility<\/h3>\n\n\n\n
The steps described in this section have been tested on tmux versions 3.1 and 3.3 on a vanilla Debian 11 installation. They should be applicable to all recent tmux versions.<\/p>\n\n\n\n
Note:<\/strong> On security-hardened Operating Systems, such as those involving SELinux, changing groups and permissions can need additional steps. Discussing those is beyond the scope of this guide. It is assumed you know how to change groups and permissions on your Operating System.<\/p>\n\n\n\n
Tmux version 3.3 (released in June 2022) introduced security related changes in the way session sharing works. These changes involve the use of the newly added server-access<\/code> command. Check the version of your tmux installation using tmux -V<\/code>. In practice, this leads to one additional step for tmux versions 3.3 and higher.<\/p>\n\n\n\n
System Description<\/h3>\n\n\n\n
Consider a system with two users: user1<\/code> with UID 1001 and user2<\/code> with UID 1002.<\/p>\n\n\n\n
In order for user2<\/code> to connect to tmux sessions created by user1<\/code>, user2<\/code>) must have access to the socket of the server created by user1<\/code> so that clients created by user2<\/code> can communicate with the server created by user1<\/code>, and (for versions 3.3 and higher) have access to the server, granted by user1<\/code> with the server-access<\/code> command.<\/p>\n\n\n\n
In following the steps below, use the appropriate user IDs and usernames based on your own system. Check the UID (and other details) of a user user1<\/code>:<\/p>\n\n\n\n
$ id user1\n<\/code><\/pre>\n\n\n\n
The command id<\/code> without any parameters shows the UID (and other details) of the current user.<\/p>\n\n\n\n
If there are no additional user accounts on your system, create a new user<\/a> before testing these steps.<\/p>\n\n\n\n
Steps<\/h3>\n\n\n\n
The steps below describe how user1<\/code> can grant access to its tmux sessions to user2<\/code>.<\/p>\n\n\n\n
\n
In a terminal session, log in as user1<\/code>.<\/li>\n\n\n\n
Start a tmux session:$ tmux <\/code>This will create the socket (sub)directory if it did not previously exist.<\/li>\n\n\n\n
Check the ownership and permissions for the socket directory:$ ls -hdl \/tmp\/tmux-1001<\/code><\/li>\n\n\n\n
Create a common group for user1<\/code> and user2<\/code>, this will make it easier to manage permissions. Create a new group tmuxusers<\/code>:# groupadd tmuxusers<\/code><\/li>\n\n\n\n
Add user1<\/code> and user2<\/code> to this group:# usermod -a -G tmuxusers user1 # usermod -a -G tmuxusers user2<\/code><\/li>\n\n\n\n
Change the group of the \/tmp\/tmux-1001<\/code> directory to tmuxusers<\/code>:# chgrp -R tmuxusers \/tmp\/tmux-1001<\/code><\/li>\n\n\n\n
user2<\/code> needs full access to the sockets of tmux servers started by user1<\/code>. Give the group full permissions on the directory:# chmod -R g+rwx \/tmp\/tmux-1001<\/code><\/li>\n\n\n\n
Verify that the group of the directory has been changed to tmuxusers<\/code> and that the group has full permissions on the directory:$ ls -hdl \/tmp\/tmux-1001<\/code><\/li>\n\n\n\n
Exit the running tmux session:$ exit<\/code><\/li>\n\n\n\n
As user1<\/code> (again), create a new tmux session and specify the name of the socket:$ tmux -L socket1<\/code><\/li>\n\n\n\n
The -L<\/code> option creates a named socket socket1<\/code>, with the path \/tmp\/tmux-1001\/socket1<\/code>.<\/li>\n\n\n\n
All commands so far are applicable on all recent versions of tmux. The next 3 commands are only for tmux version 3.3 and higher.
Within the newly created tmux session, give user2<\/code> access to the tmux server:$ tmux server-access -w -a user2<\/code><\/li>
The above command gives user2<\/code> write access to the session. So, user2<\/code> can also enter commands in the session. It is possible to give user2<\/code> only read access. With read access, user2<\/code> can only view the contents of the session but cannot enter any commands. To give user2<\/code> read access, use -r<\/code> instead of -w<\/code> in the above command:$ tmux server-access -r -a user2<\/code><\/li>
user1<\/code> can revoke the permissions granted to user2<\/code>:$ tmux server-access -d user2<\/code><\/li><\/ol>The previous three commands are only for tmux version 3.3 and higher. Further steps are applicable to all recent versions of tmux.<\/li>\n\n\n\n
Change the group of the new socket file:# chgrp tmuxusers \/tmp\/tmux-1001\/socket1<\/code><\/li>\n\n\n\n
Verify that the group of the socket file is tmuxusers<\/code> and that group has access to the file:# ls -l \/tmp\/tmux-1001\/socket1<\/code><\/li>\n\n\n\n
Check the ID(s) of the open session(s):$ tmux ls<\/code><\/li>\n\n\n\n
In another terminal, log in as user2<\/code>. Start tmux and specify the path of the named socket created by user1<\/code>:$ tmux -S \/tmp\/tmux-1001\/socket1 ls <\/code>The above command shows the list of sessions on the server started by user1<\/code> and listening on socket1<\/code>.<\/li>\n\n\n\n
Attach to the session:$ tmux -S \/tmp\/tmux-1001\/socket1<\/code><\/li>\n\n\n\n
If there are many open sessions, attach to a specific session (whose ID is N):$ tmux -S \/tmp\/tmux-1001\/socket1 attach -t N<\/code><\/li>\n<\/ol>\n\n\n\n
user2<\/code> is now connected to the tmux session of user1<\/code>.<\/p>\n\n\n\n
Using Nested Sessions<\/h2>\n\n\n\n
In general, using nested sessions in tmux is neither necessary nor recommended. It is, however, useful when connecting to a remote tmux session from within a local tmux session. Suppose you are in a tmux session on the local computer. In one of the panes (or windows), you log in to a remote server which also has running tmux sessions. When you connect to a tmux session on this remote server, you end up with nested sessions. The remote tmux session is nested inside the local tmux session.<\/p>\n\n\n\n
To pass a key sequence to the nested session, consecutively press the prefix key combination for both sessions. Assuming that both sessions use the default prefix key, press CTRL<\/kbd>+B<\/kbd> twice to access the nested session.<\/p>\n\n\n\n
For example, to do a vertical split in the nested session, enter: CTRL<\/kbd>+B<\/kbd>, followed by (again), CTRL<\/kbd>+B<\/kbd>, then %<\/kbd>.<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","manualknowledgebasecat":[242],"manual_kb_tag":[],"_links":{"self":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3756"}],"collection":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/comments?post=3756"}],"version-history":[{"count":1,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3756\/revisions"}],"predecessor-version":[{"id":3757,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb\/3756\/revisions\/3757"}],"wp:attachment":[{"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/media?parent=3756"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manualknowledgebasecat?post=3756"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/support.aklwebhost.com\/wp-json\/wp\/v2\/manual_kb_tag?post=3756"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}