Tabby doesn't work with WinSCP

[AlexWaha]

WinSCP support was mentioned in previous release notes, but it doesn't work. Documentation is not provided.

If we run WinSCP on Win10/11 with well configured Terminal client path as "PATH_TO_TABBY\Tabby.exe" ssh -i "!" !U@!@ Connect to the server using SFTP creds, login+password Click on Open Session or press Ctrl+P Tabby had run an empty window, but nothing happened, a new session was not created.

@Eugeny If the integration with WinSCP works provide the instruction of "How To Configure". Looks like for now a lot of people struggling with it and integration doesn't work.

[artu-ole]

The release notes I read from the time when the winSCP integration was added specify that Tabby is able to launch winSCP for the current ssh session, not the other way around. https://github.com/Eugeny/tabby/releases/tag/v1.0.118 That works with a hotkey or via a context menu

So the workflow goes so that Tabby is used for storing your profiles and connecting to remotes and you can open a winSCP session from it whenever file browsing/copying is needed.

What you ask would be a feature request I believe.

GitHub

Release Alpha 118 · Eugeny/tabby

Fixed random freezes when using ConPTY on Windows Added WinSCP integration (open WinSCP for the active SSH connection) - available from the context menu Added a hotkey to focus all panes simultaneo...

[AlexWaha]

Very interesting, so if I understand you right. I need to keep all my creds in Tabby. I have a hundred connections in WinSCP and the only thing that I need is to run Tabby when I need to open the console for the active connection in WinSCP not by the opposite way. With Putty, it works like I described. This and it's good, but, there is no Tabs which makes work with multiple windows harder.

[AlexWaha]

I think it may be better not to be self-concentrated on Tabby, it's just an add-on to all other SFTP/FTP clients. When Tabby will do the same as WinSCP + SSH stuff then you will be good. Otherwise, it must create a new SSH connection when it is requested by other clients, but not by Tabby itself.

There is a big issue in profiles between Tabby + WinSCP, cuz both have profiles and they are not synced with each other. But I think it better to add a function to call Tabby from WinSCP (as putty) when it is needed.

[artu-ole]

Interesting take that Tabby is just an add-on to all other SFTP/FTP clients. A take hard to agree with though as Tabby offers a comprehensive terminal emulation experience that extends beyond the capabilities of traditional file transfer clients like WinSCP. Unlike WinSCP, which primarily focuses on file transfer protocols, Tabby is designed to emulate a terminal interface, allowing users to interact with remote or local systems via various shell protocols such as SSH, Telnet, serial, WSL, PowerShell, etc. Additionally, Tabby offers features such as support for SSH agent forwarding, port forwarding, and tunneling, making it a versatile tool for various networking and system administration tasks. As for profiles, one can use standard ssh config file to store ssh connection configurations that Tabby can use out of the box and they will work with apps like vs code as well. https://code.visualstudio.com/blogs/2019/10/03/remote-ssh-tips-and-tricks#_ssh-configuration-file i.e. there is no need to be self-concentrated on Tabby if you don't want to. While I'm not saying that this would not be a useful feature, in my experience shell access is the primary way of connection, but YMMV. IMO, https://github.com/Eugeny/tabby/issues/4946 would be a better candidate to implement as, like you mentioned, you would not see a need for the feature if Tabby was able to do what winSCP does and current sftp functionality in tabby albeit exists but very limited. Though give it a try if you haven't, it's often enough for trivial use cases.

Visual Studio Code Remote SSH Tips and Tricks

Visual Studio Code Remote-SSH Tips and Tricks

[AlexWaha]

@artu-ole I can agree, but still. Not all use VScode and even if you don't like the WinSCP it doesn't mean that you should ignore the request from people that like to use WinSCP. Most of the WinSCP users want to escape from PUTTY and use TABBY in the same way as PUTTY. Just Imagine that I have 98 profiles in WinSCP and I definitely don't want to migrate manually to Tabby + I need to have a file transfer functionality. I can edit some files directly from WinSCP and at the same time, I need to get Terminal with the current SFTP connection. But what if I have 10+ active sessions? Tabby provides a good UI to have those connections in Tabs, a very good feature.

I hope you understand my POV. Please just create some addon for WinSCP that allows to use Tabby as Putty.