Faro is a desktop client for SFTP, FTP/FTPS, SSH, S3-compatible storage, and a dozen other backends. It's been on GitHub and shipping releases for a while now — v1.3.29 today — this is just the first time I've posted it here. Why it exists: I had FileZilla open for SFTP, PuTTY for shells, and the AWS console in a browser tab. Three connection lists, three mental models, nothing shared between them. Faro is one connection list and one dual-pane window over all of it, with a terminal tab running against the same SSH session you're browsing in the other pane. Structurally it's one Rust trait, RemoteFs. A backend is one impl plus one builder, and then the file browser, transferage treemap, directory diff, search, and the CLI pick it up without changes. That's why the list got long: SFTP, FTP/FTPS, S3-compatible (AWS, R2, B2, Wasabi, MinIO, Spaces, Storj...), Azure Blob, GCS, Wx, OneDrive, Google Drive, Box, plus Shopify themes and HubSpot CMS files browsed like an FTP site. The Agent Bridge is the newer piece. I wanted Claude Code to be able to work on a server without me handing it a private key or installing a daemon on the box. So Faro lends the session it already has open: localhost-only HTTP/MCP server, bearer token generated per launch, off by default on every connection, and each exec pops a prompt with the exact command before it runs. Approvals and denials land in an audit log in the panel. Rough edges, so nobody's surprised: builds aren't signed yet, so macOS needs a one-time `xattr -cr /Applications/Faro.app` → Run anyway". No auto-updater. Sync is one-way only for now. There's no landing page — the README is it. MIT, Windows/macOS/Linux. If a backend you use is missing, tell me; one impl is usually a weekend.

Faro

The file manager for servers, buckets, and AI agents

The file manager for servers, buckets, and AI agents