While I have no issues with SFTP, I do think that the reliance on an increasing number of unmaintained or poorly maintained third party packages is a problem that needs to be addressed.

For example, LaTexTools, which is a popular plugin and important for many who use ST primarily for writing has been unmaintained for 6 years now. It’s a mature product so it isn’t too broken yet, but unless someone takes responsibility for it some day it will be. At that point, I would start to look for a new editor to use, even though I really love ST.

The underlying problem is perhaps a decline in the overall user base of ST. I understand that the strategy of ST has always been to provide a great base for others to extend with plugins. That worked well in the past. But when the times change it might be a good idea to update the strategy, don’t you think?

It’s been three years since I’ve used Sublime Text 3 with the Codex SFTP plugin (along with phpBB and XDebug). I updated my version of ST, reinstalled my Codex license, updated my sftp-config.json (I’m on a new server now), and followed the steps here, as I did three years ago. As I write, I’m syncing Remote -> Local, literally thousands of files. It’s working like a champ.

My experience today is no different than it was three years ago. I’m not seeing the issue.

I have developed a new SFTP plugin that supports SFTP, FTPS, and WEBDAV4. The main reason I created a new plugin is what everyone is experiencing here with the plugin not working correctly with newer sublime text 4, The issue is the SFTP plugin from codex causes newer versions of sublime text to load the SFTP plugin from in python 3.3, or legacy mode and there is several race condition issues that cause things to break or to not operate correctly in the sublime API. The compiled plugin creates python cache and if you upgrade your version of sublime text without clearing this you will have issues.

I am developing useful and efficient plugins for sublime text as I feel sublime has the best non cluttered interface and layout on MacOs.

Here is a few screenshot os my snoopsSFTP plugin, as I also work on my own trained AI model called SNOOPS. Feel free to let me know what you guys think.

Screenshot 2025-03-23 at 12.12.45 PM.jpg1348×1714 196 KB

Screenshot 2025-03-23 at 12.14.09 PM.png1384×824 45.1 KB

Screenshot 2025-03-23 at 12.14.20 PM.png1300×578 32 KB

Screenshot 2025-03-23 at 12.19.42 PM.png1338×610 56.3 KB

If that’s the case, you are using an out-dated version. Current versions certainly run on python 3.8.

Since Sublime Text Build 4205, the Will Bond’s SFTP and SVN plugins no longer work. They can also no longer be installed via Package Control.

I sorely miss these two tools, for which I once purchased a license.

I would be very grateful if Will Bond could resolve this issue.

I’ll also open a ticket about this on codexns.io. Hopefully, there will be a solution soon.

I have also encountered this issue recently (with ST build 4205). I have also opened a ticket with Codex at https://codexns.io/products/sftp_for_sublime/support … Hoping to get a resolution soon.

After poking through ~/Library/Application Support/Sublime Text 3/Packages/SFTP/SFTP.py it seems the plugin is failing to import from sftp.commands starting at line 106 because of the error:

no module named 'sftp'

It’s quite an inconvenience for me, too. I rely on this package.

Still, I think that SFTP support should be integrated in ST, not a plugin. Especially after many years of stagnating development.

Any reason why you cannot team Subl with PuTTY SSH Client? I am curious since I will be using SFTP soon with a hosting site. Also FileZilla. It is just orchestration of readily available tools. Does it need to be embedded in Subl? Swiss army knife model.

I can team ST with PuTTY, with Mutagen, I can even write my own tool. It would be great if I didn’t have to deal with an external tool for something I do all the time, like opening and saving files. External tools sometimes break (like, for example, the SFTP plugin we’re talking about here) and that’s pretty annoying. Moreover, it wouldn’t break “swiss army knife” model: if you’re not interested in the integrated SFTP feature, just don’t use it.

Many other code editors and IDEs offer this feature. Or, at least, the plugin is maintained by people very close to the editor’s main developers, preventing breakages due to upgrades.

I have the same problem and I have no answer regarding the tickets I posted on support

I still get the following output when I try to install the SFTP package:

Package Control: Installed package “SFTP” 2.1.0
Package Control: Package SFTP successfully installed
ignored packages updated to: [“Vintage”]
reloading settings Packages/User/Package Control.sublime-settings
reloading plugin SFTP.SFTP
error: SFTP

The SFTP package seems to have been installed using an older version of Package Control. Please remove the SFTP package, upgrade Package Control to 2.0.0 and then reinstall SFTP.

It may be necessary to delete the “Packages/Package Control/” folder and then follow the instructions at https://packagecontrol.io/installation to properly upgrade Package Control.
generating syntax summary

I once paid money for this and now I can’t use it anymore. All support requests on codexns.io remain unanswered.

Is there any solution?

Can anybody help?

Btw. Same problem with the SVN package!

I know this is not originally ST related but I hope Will also reads here.

@wbond I tried to get an answer on codexns.io for over a month with no response at all. The problem is that SFTP and SVN has stopped working with the recent ST version. Is a solution being worked on for this?

I have been working on a new version to support changes in the latest dev build of ST.

If SFTP is key to your development, please stay on the stable build of Sublime Text for now!

I switched back to Build 4200 for now. SFTP is working again. Thanks for your quick reply!

That’s a fair point. Since third-party plugins are developed and maintained independently, the plugin author is usually the best person to contact for support, especially if it’s a paid plugin. The community can certainly offer suggestions based on experience, but there’s no guarantee that someone will be able to provide a solution. Reaching out to the developer directly is often the quickest and most reliable way to resolve plugin-specific issues.

I have support questions into Codexns that are 2 years old - no answer. How can a developer expect to be taken seriously when they treat paying customers this way? My company would cease to exist if we acted like that.

If there is another FTP plugin that actually works and is supported, I’d love to have it. I have found Sublime Text to be an excellent code editor on Linux and I have tried a lot of them. I have no plans to change.

You could give this plugin a try (ftr: I did not yet, but others liked it): https://packages.sublimetext.io/packages/RemoteSync

Hello !
I love your plugin it is absolutely key to my development and would gladly pay for a new license if necessary…
But today was the day is doesn’t work anymore on the stable build of Sublime Text. I did revert to an older working build but I think that if you can’t upgrade your package (and I understand why, I know it is a lot of work) I will look for a replacement.
Anyway, I have been using your plugin for more than 10 years and I am really thankfull for your work.

I have a new version that I’ve updated and tested against 3.14. It’s very close to shipping.

Sorry for not having it in place by today!

SFTP v3.0 has been released.

Please see SFTP v3.0 – for Sublime Text 4205+ for instructions on updating until the new version is picked up by Package Control.