So, I understand the value of tmux for detaching and restoring sessions. What I don't really understand is why I'd want to use something like this instead of tiling and managing sessions / windows / panes within my terminal emulator. Kitty has tremendous support for all kinds of features, including capturing and processing the output from commands, piping scrollback buffers to external commands, scrolling to previous command prompts, searching and highlighting output dynamically, and much more besides. The overlap is significant between tools like this and tools like kitty or iTerm. Am I missing some advantage in putting this functionality on the server rather than the client?
Taking it even one step further, I probably would really be better off managing the window tiling in my window manager, however, I still have yet to settle on a tiling window manager that works well enough under wayland and supports everything I need well enough to give up the Gnome shell. I did try https://github.com/YaLTeR/niri this past weekend and it's pretty great. niri is inspired by PaperWM. I used PaperWM for a while and it was pretty awesome but suffers from the same issue as all of the tiling extensions for Gnome shell: they are never stable enough for for my daily use because Gnome is a moving target and the gnome shell extension API isn't really up to the task of radically transforming the window management paradigm. Projects like PaperWM have too many downsides that are really difficult to overcome, despite their significant innovation and appealing UX.
One big use case is the ability to attach/re-attach to sessions running on some remote host. When connection is lost, you don't lose the session and can easily re-attach to it
