hop

I used tmux for about a decade and wrote quite a bit of automation around it, including tmux_super_fingers. But eventually I got frustrated with project sessions being limited to terminal windows. In particular, the browser tabs belonging to those projects were all mixed up in a single browser window. So I wrote hop[1], which uses sway workspaces instead of tmux sessions. Terminals, editors, browsers, or any other windows really, can now all belong to the same project. What I hadn't quite anticipated was how liberating it would feel to use the system's own tools - windows, workspaces, clipboard, scrollback, etc. - instead of tmux's alternatives. No more two layers of window management or competing keybindings. On top of that, hop has proven to be a great fit for working in sandboxed environments. With tmux, sessions are tied to a tmux server running on a particular machine or inside a particular container. With hop, local, containerized or remote (or both) are all allied under one banner. I realise most folks won't be able to use it - it requires rather extravagant tool choices (notably, sway) - but it's an interesting experiment nonetheless. And it's been working great for me for months now. [1] artemave/hop

Show HN: I replaced tmux with sway workspaces

One thing you might be missing is better integration between the local desktop and the remote environment. Things like persistent ssh connections, seamless clipboard sharing (including images), port forwarding and file path translation, so that working remotely feels almost indistinguishable from working locally. I wrote a session manager[1] to handle all that. Linux/sway/kitty only though. [1] artemave/hop