While building DartShell on macOS, I ran into a migration issue that a successful SSH login did not reveal.
The terminal reconnected correctly after a dropped session. I could run commands again and browse the remote directory, yet dragging a local file into that directory sometimes failed to start an upload. In another case, the transfer entered the queue while the sidebar continued showing stale status.
That failure changed how I evaluate a Bitvise replacement: reconnect SSH, then verify that SFTP uploads still work.
The Bitvise behavior I needed to preserve
Bitvise SSH Client gives Windows developers a practical combination of SSH access and graphical file management. After saving the host, port, username, and authentication settings, I can open a terminal and browse remote files from the same client.
