Remote Files

Remote Files shows the files of the host of the session in view, or of the host picked above the list, as a tree with columns (name with the icon of its kind, size, kind, modified), the same tree the Assets of projects use: folders unfold in place, and `..` goes up. It starts at the home of the user and remembers the folder of each host. Above the list, aligned left after "Current path:", are the folders on the way, each a link back up; then a filter for the folder.

Each row shows the icon of what it is, its name (and where a link points), its size and when it changed. A click enters a folder; a double click opens a file. Text opens in the editor, images and PDFs in their viewers, and anything else is downloaded to the Downloads folder. The menu of a row opens, downloads, uploads (Upload File Here on a folder), renames, copies the path or deletes (asking first). The header creates a folder or a file, and shows its buttons only while a folder is on screen.

Files go through the system ssh client, prepared like the sessions of the host, so jump hosts, keys, passwords and VPNs apply. Each host gets a master connection (ControlMaster) that later commands reuse without logging in again. Files are read and written as raw bytes; a file written back keeps its owner and permissions.

What it does

• Follows the session in view, or any host picked.
• A tree with columns and file icons, shared with project assets; breadcrumb, folder filter, sizes and dates.
• Open text, images and PDFs; download anything else.
• Upload, new folder, new file, rename, copy path, delete.
• One reusable SSH master connection per host.

How it behaves

• Every file action goes to the log, under files.

Why it matters

• No separate SFTP client: the files of a server sit beside its shell.