Github url


by tmuxinator

tmuxinator /tmuxinator

Manage complex tmux sessions easily

10.1K Stars 589 Forks Last release: 2 months ago (v2.0.1) MIT License 828 Commits 49 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


Gem Version Build Status Coverage Status Code Climate Dependency Status Gitter

Create and manage tmux sessions easily.

| Screenshot |



gem install tmuxinator


brew install tmuxinator

tmuxinator aims to be compatible with the currently maintained versions of Ruby.

Some operating systems may provide an unsupported version of Ruby as their "system ruby". In these cases, users should use RVM or rbenv to install a supported Ruby version and use that version's


binary to install tmuxinator.

Editor and Shell

tmuxinator uses your shell's default editor for opening files. If you're not sure what that is type:

echo $EDITOR

For me that produces "vim". If you want to change your default editor simply put a line in ~/.bashrc that changes it. Mine looks like this:

export EDITOR='vim'


The recommended version of tmux to use is 1.8 or later, with the exception of 2.5, which is not supported (see issue 536 for details). Your mileage may vary for earlier versions. Refer to the FAQ for any odd behaviour.


Your distribution's package manager may install the completion files in the appropriate location for the completion to load automatically on startup. But, if you installed tmuxinator via Ruby's


, you'll need to run the following commands to put the completion files where they'll be loaded by your shell.


# wget -O /etc/bash\_completion.d/tmuxinator.bash


# wget -O /usr/local/share/zsh/site-functions/\_tmuxinator

Note: ZSH's completion files can be put in other locations in your


. Please refer to the manual for more details.


$ wget ~/.config/fish/completions/


A working knowledge of tmux is assumed. You should understand what windows and panes are in tmux. If not please consult the man pages for tmux.

Create a project

Create or edit your projects with:

tmuxinator new [project]

Create or edit a local project where the config file will be stored in the current working directory (in


) instead of the default project configuration file location (e.g.



tmuxinator new --local [project]

For editing you can also use

tmuxinator open [project]



is aliased to






, and




. Please note that dots can't be used in project names as tmux uses them internally to delimit between windows and panes. Your default editor (


) is used to open the file. If this is a new project you will see this default config:

# ~/.tmuxinator/sample.yml name: sample root: ~/ # Optional tmux socket # socket\_name: foo # Note that the pre and post options have been deprecated and will be replaced by # project hooks. # Project hooks # Runs on project start, always # on\_project\_start: command # Run on project start, the first time # on\_project\_first\_start: command # Run on project start, after the first time # on\_project\_restart: command # Run on project exit ( detaching from tmux session ) # on\_project\_exit: command # Run on project stop # on\_project\_stop: command # Runs in each window and pane before window/pane specific commands. Useful for setting up interpreter versions. # pre\_window: rbenv shell 2.0.0-p247 # Pass command line options to tmux. Useful for specifying a different tmux.conf. # tmux\_options: -f ~/.tmux.mac.conf # Change the command to call tmux. This can be used by derivatives/wrappers like byobu. # tmux\_command: byobu # Specifies (by name or index) which window will be selected on project startup. If not set, the first window is used. # startup\_window: editor # Specifies (by index) which pane of the specified window will be selected on project startup. If not set, the first pane is used. # startup\_pane: 1 # Controls whether the tmux session should be attached to automatically. Defaults to true. # attach: false windows: - editor: layout: main-vertical # Synchronize all panes of this window, can be enabled before or after the pane commands run. # 'before' represents legacy functionality and will be deprecated in a future release, in favour of 'after' # synchronize: after panes: - vim - guard - server: bundle exec rails s - logs: tail -f log/development.log


The windows option allows the specification of any number of tmux windows. Each window is denoted by a YAML array entry, followed by a name* and command to be run.

*Users may optionally provide a null YAML value (e.g.




) in place of a named window key, which will cause the window to use its default name (usually the name of their shell).

windows: - editor: vim

Window specific root

An optional root option can be specified per window:

name: test root: ~/projects/company windows: - small\_project: root: ~/projects/company/small\_project panes: - start this - start that

This takes precedence over the main root option.


**_Note that if you wish to use panes, make sure that you do not have


in your project name. tmux uses


to delimit between window and pane indices, and tmuxinator uses the project name in combination with these indices to target the correct pane or window._**

Panes are optional and are children of window entries, but unlike windows, they do not need a name. In the following example, the


window has 2 panes, one running vim, the other guard.

windows: - editor: layout: main-vertical panes: - vim - guard

The layout setting gets handed down to tmux directly, so you can choose from one of the five standard layoutsor specify your own.

Please note the indentation here is deliberate. YAML's indentation rules can be confusing, so if your config isn't working as expected, please check the indentation. For a more detailed explanation of why YAML behaves this way, see this Stack Overflow question.

Note: If you're noticing inconsistencies when using a custom layout it may be due #651. See this commentfor a workaround.

Interpreter Managers & Environment Variables

To use tmuxinator with rbenv, RVM, NVM etc, use the



pre\_window: rbenv shell 2.0.0-p247

These command(s) will run before any subsequent commands in all panes and windows.

Custom session attachment

You can set tmuxinator to skip auto-attaching to the session by using the



attach: false

If you want to attach to tmux in a non-standard way (e.g. for a program that makes use of tmux control mode like iTerm2), you can run arbitrary commands by using a project hook:

on\_project\_exit: tmux -CC attach

Passing directly to send-keys

tmuxinator passes commands directly to send keys. This differs from simply chaining commands together using




, in that tmux will directly send the commands to a shell as if you typed them in. This allows commands to be executed on a remote server over SSH for example.

To support this both the window and pane options can take an array as an argument:

name: sample root: ~/ windows: - stats: - ssh [email protected] - tail -f /var/log/stats.log - logs: layout: main-vertical panes: - logs: - ssh [email protected] - cd /var/logs - tail -f development.log


Project files support ERB for reusability across environments. Eg:


You can also pass arguments to your projects, and access them with ERB. Simple arguments are available in an array named




bash $ tmuxinator start project foo
# ~/.tmuxinator/project.yml name: project root: ~/ ...

You can also pass key-value pairs using the format


. These will be available in a hash named




bash $ tmuxinator start project workspace=~/workspace/todo
# ~/.tmuxinator/project.yml name: project root: ~/ ...

Starting a session

This will fire up tmux with all the tabs and panes you configured,


is aliased to



tmuxinator start [project] -n [name] -p [project-config]

If you use the optional


argument, it will start a new tmux session with the custom name provided. This is to enable reuse of a project without tmux session name collision.

If there is a


file in the current working directory but not a named project file in


, tmuxinator will use the local file. This is primarily intended to be used for sharing tmux configurations in complex development environments.

You can provide tmuxinator with a project config file using the optional


argument (e.g.



-p path/to/my-project.yaml

). This option will override a


name (if provided) and a local tmuxinator file (if present).


The shell completion files also include a shorthand alias for tmuxinator that can be used in place of the full name*.

mux [command]



alias has been removed from the Zsh completion script because it was resulting in unexpected behavior in some setups. Including aliases in completion scripts is not standard practice and the Bash and Fish aliases may be removed in a future release. Going forward, users should create their own aliases in their shell's RC file (e.g.

alias mux=tmuxinator


Other Commands

Copy an existing project. Aliased to



tmuxinator copy [existing] [new]

List all the projects you have configured. Aliased to



tmuxinator list

Remove a project. Aliased to

tmuxinator delete [project]

Remove all tmuxinator configs, aliases and scripts. Aliased to

tmuxinator implode

Examines your environment and identifies problems with your configuration

tmuxinator doctor

Shows tmuxinator's help. Aliased to

tmuxinator help

Shows the shell commands that get executed for a project

tmuxinator debug [project]

Shows tmuxinator's version.

tmuxinator version

Project Configuration Location

Using environment variables, it's possible to define which directory tmuxinator will use when creating or searching for project config files. (See PR #511.)

Tmuxinator will attempt to use the following locations (in this order) when creating or searching for existing project configuration files:

  • $XDG\_CONFIG\_HOME/tmuxinator
  • ~/.tmuxinator


Window names are not displaying properly?


export DISABLE\_AUTO\_TITLE=true

to your





To contribute, please read the contributing guide.


Copyright (c) 2010-2020 Allen Bargi, Christopher Chow. See LICENSE for further details.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.