Feature description
Is your feature request related to a problem? Please describe.
I have several legacy project servers that only support FTP/SFTP connections for file transfers, and do not allow SSH shell access due to security policies. Currently, I cannot use Wave Terminal to manage files on these servers directly, and have to rely on separate FTP clients, which breaks my workflow.
I would like Wave Terminal to support FTP and SFTP protocols as additional file system backends, similar to how wsh currently handles file operations with wsh://local/ paths.
Ideally, I could use commands like:
This would allow seamless file management across local, remote SSH, and legacy FTP/SFTP servers within the same wsh command ecosystem, making Wave Terminal a unified file management hub.
Describe alternatives you've considered
- Using a standalone FTP client (works but breaks workflow integration and requires context switching)
- Mounting FTP via third-party tools like
curlftpfs or sshfs (unstable, requires extra dependencies and setup)
- Deploying
wsh directly on the legacy server (not possible due to restricted environments and lack of shell access)
- Using
sftp command-line tool in a terminal block (works, but lacks integration with wsh file commands and Wave's unified file management)
Additional context
- The project already shows signs of extensible file system backends (e.g., S3 support), so adding FTP/SFTP as a new
fileshare module may be architecturally feasible.
- SFTP uses the SSH protocol, which might be partially reusable from the existing SSH connection logic in the codebase.
- Many developers still maintain legacy systems that only expose FTP/SFTP interfaces, so this feature could benefit a significant number of users.
Implementation Suggestion
No response
Anything else?
No response
Feature description
Is your feature request related to a problem? Please describe.
I have several legacy project servers that only support FTP/SFTP connections for file transfers, and do not allow SSH shell access due to security policies. Currently, I cannot use Wave Terminal to manage files on these servers directly, and have to rely on separate FTP clients, which breaks my workflow.
I would like Wave Terminal to support FTP and SFTP protocols as additional file system backends, similar to how
wshcurrently handles file operations withwsh://local/paths.Ideally, I could use commands like:
This would allow seamless file management across local, remote SSH, and legacy FTP/SFTP servers within the same
wshcommand ecosystem, making Wave Terminal a unified file management hub.Describe alternatives you've considered
curlftpfsorsshfs(unstable, requires extra dependencies and setup)wshdirectly on the legacy server (not possible due to restricted environments and lack of shell access)sftpcommand-line tool in a terminal block (works, but lacks integration withwsh filecommands and Wave's unified file management)Additional context
filesharemodule may be architecturally feasible.Implementation Suggestion
No response
Anything else?
No response