> as someone who dislikes config files to an extreme degree This tool has a config as well. From the repos readme: Viking saves data locally. Set VIKING_C

> as someone who dislikes config files to an extreme degree This tool has a config as well. From the repos readme: Viking saves data locally. Set VIKING_CONFIG_DIR env variable for a custom directory. Use viking config to check the current config folder. > hidden information What exactly is "hidden" about ~/.ssh/config ? It's a plaintext file in a format that is the same across every single machine that uses openssh, which is pretty much every *nix box on the planet. > commands stop being portable How is using literal `ssh` not portable? If you're talking about the ssh config: That is a plaintext file that can be checked into a repo and simply downloaded to any machine I want. And again: viking too has a config. > a modern cli host=$( awk '$1 == "Host" && $2 != "*" {print $2}' "$HOME/.ssh/config" | fzf --reverse ) [[ -n host ]] && ssh "$host" There. I just built a modern, interactive tool to chose a server from my ssh config. It requires only fzf as a non-standard dependency, a tool that is present in pretty much every package repository. > allows me to manage my configurations vim ~/.ssh/config There. A powerful, searchable, portable way to manage my SSH configuration. I can even use comments, and have access to all ssh settings available. All dependencies come preinstalled on most *nix boxes.