Moving over
What it takes
There is nothing to migrate: keep using ssh where it wins, and let Vandle hold the connections you would otherwise click together in three tools.
You already have the config file memorised
A well-kept ssh_config is hard to beat, and Vandle does not try to replace it. It answers the parts a config file cannot: an inventory you can see, a file surface, a remote desktop, and a route per connection.
Credit where it is due
ProxyJump, ControlMaster and a tidy Host block will outlive every GUI, and anything scriptable belongs on the command line. That is not the part that hurts.
What changes
Four things you get that you did not have.
- An inventory you can look at, grouped in folders, with one row per protocol per machine.
- A file surface for the transfers that currently mean remembering scp argument order.
- Remote desktop beside the shells instead of a second application with a second inventory.
- Routes as objects: assign one to a connection or a whole folder instead of repeating ProxyCommand blocks.
Side by side
the OpenSSH command line and Vandle
| Aspect | the OpenSSH command line | Vandle |
|---|---|---|
| Inventory | ssh_config, read by you | A visible list, grouped, colour-coded per protocol |
| Files | scp and sftp per command | A file surface with multi-select and a split view |
| Desktops | Not covered | RDP on a native surface, beside the shell |
| Automation | Excellent | Unchanged. The shell stays the shell. |
And the rest of it
Four more protocols came along
Replacing one tool gets you five. Whatever else that machine speaks is already a row on the same record - and every one of them takes the route you assigned.
Web
Real browsing, properly routed
SSH
A terminal that keeps up
SFTP
Two remote panes, no detour
WebDAV
The other half of file transfer
RDP
Desktops on a native surface
Local
Your own machine, in the same list
Also compared