The real interface — a 1.2 GB clip streaming straight to Downloads
One session per machine — list, preview, rename, upload, delete. The bytes never detour through a server: they ride the mesh straight between the two disks, end to end.
A download registers a backend sink first, then asks — so the first chunk can't race the registration — and the bytes stream directly into Downloads, never through the window. Uploads go up in chunks, each one awaiting the daemon hand-off, so a slow mesh applies backpressure instead of ballooning memory.
Click a file and it opens right in the window — source code, markdown, JSON and logs in monospace; images scaled to fit. There's a 10 MB cap on what gets pulled over the wire just to look at; anything bigger says so, and points you at the download instead.
Files open only for machines you own or that are in your fleet — a guest can't even ask. The files host walks the disk as the remote user, with their filesystem permissions, so you see exactly what you'd see sitting at the keyboard. Nothing more.
Files are owner/fleet only: if you haven't claimed this machine, do that from the graph first.
Open the graph →Connecting, listing, empty, transferring, armed to delete, previewing — each state looks different, and tells you exactly what's happening on the far side.
The route's negotiating. The machine's name and a plain diagnostic stand in.
The host's listing landed; folders first, then files, sorted by name.
No entries to show — the list says so rather than sitting blank.
The progress bar fills, then the row flips green: saved to Downloads.
First click arms — the ✕ becomes "sure?" for 3.5 seconds; a second click acts.
Text and images render in the pane; anything else points at the download.