Tmux

The first time it bit me I was halfway through a database migration over SSH. Train hit a tunnel, WiFi blinked, connection gone. The process running on the other end went with it. I sat there staring at a dead prompt wondering how much of the migration had actually committed. A terminal multiplexer would have saved me. The process keeps running on the server whether I’m attached or not, so a dropped connection becomes a non-event. I reconnect, reattach, and the work is exactly where I left it. That property alone is worth the setup cost, and it’s why I treat a multiplexer as part of the base layer on every machine I touch. ...

Here is how a lot of us work in 2026: a dotfiles repo with years of commits, a vim config that pulls in thirty plugins, a tmux prefix remapped to something more comfortable, a shell prompt that took a weekend to get right. The setup is yours, down to the last keybinding. On your laptop, you are fast. Muscle memory does the work and you barely think about the tools at all. That is the dream we sell ourselves, and most of the time it holds up fine. ...