I developed “lssh,” a terminal-native remote access suite designed for users who manage multiple SSH targets.
It started about 10 years ago as an interactive SSH host selection tool, but now includes parallel command execution, mux-style SSH workspaces, file transfer/synchronization tools, provider-integrated inventory, and connectors for AWS SSM, EICE, WinRM, Telnet, Proxmox, GCP, Azure, and more.
One of the features I personally wanted was the ability to use my local shell environment (including vim and tmux) on a remote host without having to copy dot files or helper scripts.
Since I recently added native mux workspace support, and also add terminal to agentless monitering tool I thought it had turned into something interesting, so I decided to post it for this place.
Hello, HN.
I developed “lssh,” a terminal-native remote access suite designed for users who manage multiple SSH targets.
It started about 10 years ago as an interactive SSH host selection tool, but now includes parallel command execution, mux-style SSH workspaces, file transfer/synchronization tools, provider-integrated inventory, and connectors for AWS SSM, EICE, WinRM, Telnet, Proxmox, GCP, Azure, and more.
One of the features I personally wanted was the ability to use my local shell environment (including vim and tmux) on a remote host without having to copy dot files or helper scripts.
Since I recently added native mux workspace support, and also add terminal to agentless monitering tool I thought it had turned into something interesting, so I decided to post it for this place.
would love to know how it holds up against Boundary or just plain old ssh config + mosh for the day-to-day grind
[dead]