CLI stability fix
- Fixed a rare concurrent-write panic in the CLI signaling client. Rapid ICE candidate negotiation could trigger simultaneous WebSocket writes from separate goroutines; all writes are now serialized.
CLI output improvement
- The
Sendingsummary line (file name and total size) now appears above the sharing box, so you can see what is being sent before the peer connects.
File summary on both sides
- Both the sender and the receiver now see a file count and total size before and after the transfer. Example:
Sending 3 files · 11.8 MBon the sender side andIncoming 3 files · 11.8 MBon the receiver side.
CLI-to-CLI transfer fix
- Fixed an error reported by the CLI sender after a successful CLI-to-CLI transfer. The transfer completed correctly but the sender exited with an error code. It now exits cleanly.
One-command install and self-update
floe updatenow works on all platforms (script installs, manual installs). It downloads, verifies, and replaces the running binary in one step.- Re-running the install script (
curl -fsSL https://floe.one/install.sh | shorirm https://floe.one/install.ps1 | iex) also upgrades an existing install in place. - If floe was installed via Homebrew, Scoop, or Winget,
floe updatedetects this and prints the correct package manager command instead. - Security: updated
ws,esbuild, andpostcsstransitive dependencies to address published advisories.
Rich transfer summary
-
At the end of each transfer, the CLI now prints a boxed summary with the total data transferred, elapsed time, and average speed. Example:
-
The receiver summary also includes the
Saved topath.
Transfer reliability and browser fixes
- Fixed several CLI transfer sync bugs that could cause stalled or incomplete transfers, especially in CLI-to-CLI sessions. Added cross-implementation loopback tests to prevent regressions.
- Fixed a browser receiver bug where a
Bufferview was retained across chunk boundaries instead of being copied, which could corrupt received data. - Fixed an issue where the in-app browser detection could steal the receiver slot from a legitimate peer, preventing the transfer from starting.
- Fixed duplicate WebRTC signal handling that could break transfers after a reconnect.
- Redesigned the in-app browser warning page for clarity.
- Upgraded the CLI to Pion WebRTC v4 (includes Pion DTLS v3).
- Performance: improved browser-to-browser transfer throughput with better backpressure tuning.
Initial public release
- Browser-based peer-to-peer file transfer at floe.one. No account, no installation, no file storage.
floeCLI for macOS, Linux, and Windows. Fully interoperable with the browser client.- End-to-end DTLS encryption on all transfers, direct and relayed.
- Optional TURN relay fallback for peers behind strict firewalls or carrier-grade NAT (capped at 2 GB per session).
- Self-hosting support via Docker Compose. See Self-Hosting.
- Mintlify documentation site at docs.floe.one.