> I was mostly using it to organise terminal windows and that was now xmonad's job.

A thing I only realized after switching to a tiling/dynamic window manager (i3), as a tmux user, is that tmux complects two things:

  * persistent pty sessions
  * pty multiplexing 

So even after switching to i3, tmux was still useful to me for the persistent sessions, to keep certain long-running programs running. I just stopped using the multiplexing. But then I learned about abduco [1] which, like dtach, only deals with terminal session management. I haven't looked back since.

[1]: http://www.brain-dump.org/projects/abduco/

The honest answer is that I keep tmux around because I'm used to it, though I do make good use of its persistent sessions and remote login interaction.

Oh also, it's the one thing that gives me terminal emulator (st) buffer history.

I use i3 with tmux. Tmux for me handles grouping of things I'm working on using sessions, every project or thing thing that I'm tinkering with gets a named session. I like that I can detach and leave a project in a state that I can easily come back to.

I also prefer to have one terminal window and organize it with tmux. Much like I only open one browser and organize it with tabs. Leaving my actual workspaces uncluttered.

I use tmux so that when I work remotely on my laptop I can connect to the same tmux session. Also, I like the vim and tmux plugins for seamless window navigation.

How do you use xmonad on OSX? From what I've seen, most people use native clients that re-create the functionality of xmonad.

Oh, I don't. I switched back to Linux.

story of my life