I also use iTerm2 on macOS, with tmux. Here are the main reasons why I do that: - I can create window splits running multiple shell sessions in each pane, and

I also use iTerm2 on macOS, with tmux. Here are the main reasons why I do that: - I can create window splits running multiple shell sessions in each pane, and then "zoom" in to an individual pane to focus on what I'm doing in that shell session. - I can organize my work into named sessions, with multiple windows within each session, and panes within each window, and navigate between these using the keyboard. - I can persist that session/window/pane structure across machine reboots (tmux-resurrect). The result is that I always have the same set of tmux shell sessions running, corresponding to the different projects that I work on. - The same keybindings for session/window/pane management work whether I'm on MacOS or on a remote linux machine running tmux. But I'm not a very advanced tmux user and there's a lot more I could do. If you look through the tmux feature set it will give you an idea of what you can do beyond what you can do with iTerm2. iTerm2 does have its own "tmux integration mode" but that's never quite appealed to me: I use tmux specifically because I want the tmux style of window splits etc, and because I want the familiar keybindings to be the same when I'm on a linux machine. So placing tmux behind the iTerm2 UI isn't what I'm personally looking for. I think! Or maybe I've misunderstood the iTerm2 feature.