What it can't do yet.
This is young software — beta, in feature freeze heading toward 1.0, which means releases from here are bug fixes and small additions, not new capabilities. A few things are deliberately missing rather than half-built. Here's the complete list, kept in sync with the README every release.
The short version: SFTP is the well-tested path. Everything else is newer.
-
FTP & FTPS
Verified against real vsftpd and proftpd servers running locally — plain FTP, active-mode fallback, the legacy
LISTparsing fallback, and a full encrypted transfer over both FTPS variants (explicit and implicit, including trusting a certificate and reusing that trust). Not yet proven against a production server out in the wild. Newer and less battle-tested than SFTP; expect some rough edges. -
Dragging out of a remote pane
Only individual files, not folders. Downloading an entire folder tree before a drag could even start would mean an unpredictable wait with no way to cancel just that one drag. Dragging in has no such limit, and there's no lazy/delayed handoff — the whole file downloads up front, even for a drag you cancel.
-
Server to server
Staged through a local temporary file: downloaded, then uploaded. No protocol lets one server hand a file straight to another. In practice that's roughly double the time and briefly uses local disk equal to the file's size. Verified end to end against two genuinely independent local SFTP servers, byte-for-byte matching.
-
Move
Can't merge into a folder that already exists at the destination — a server-side rename simply can't combine two folders. It fails with an explanation instead. Move to a new name, or use an ordinary copy when you need a real merge.
-
Pause
Works for any transfer involving a server — upload, download, or either half of a server-to-server move. A purely local copy can only be cancelled and retried, since there's nothing meaningful to interrupt mid-copy.
-
Edit in place
The editor command is a single string with the file path appended as its only argument — no
{file}-style template substitution. Works for most terminal-launched editors (code,gedit,notepad++); one needing its own argument order isn't supported yet. It also doesn't detect the same file being edited elsewhere at the same time — last save wins. -
Queue persistence
Written to disk when you close the app, not continuously, so a crash still loses what was in flight. Server-to-server transfers aren't restored at all, and finished, failed, or skipped items aren't kept — this restores pending work, not a history.
-
Permissions
One file or folder at a time, and only the standard nine read/write/execute bits. No multi-select, no recursive apply, no setuid/setgid/sticky.
-
Proxy
One global setting, not per-site: every connection uses it, or none does. An FTP/FTPS data connection is only proxied in passive mode, which is what the app always tries first — the rare active-mode fallback can't be proxied by anything client-side.
-
Ctrl+C / Ctrl+V
Always means "copy to the other pane" — no same-pane duplicate, no Ctrl+X cut. Use right-click Move Selected or an ordinary drag for moving instead. If the source pane navigates away before you paste, the paste is refused rather than silently grabbing whatever now shares those names.
-
Quick connect
Password only, and it always targets the right pane. Use Connect… for a private key or the left pane.
-
Filename filter
A simple substring match — no wildcards or regular expressions. Each pane's typed filter text clears on navigation or app close; only whether the filter row is shown at all is remembered.
-
Site export
Always exports every saved site — no way to export just a folder or a selection yet. The file is plain JSON, so trimming it by hand afterward works in the meantime.
-
macOS build
Apple Silicon only, no Intel build. Unsigned and unnotarized (no paid Apple Developer account exists for this project yet), so Gatekeeper blocks the first launch until you right-click → Open.
-
Checksum verification
Not offered for server-to-server transfers, and never runs automatically. Both deliberate: verifying means re-reading a remote file a second time (no server-side hash is reachable over SFTP or FTP), so it's on-demand for one completed transfer, not a background check.
Every release is built and put through the full automated test suite before it's published, not just compiled. This list is kept in sync with the README's own copy — if they ever drift, the README is the one to trust.