proton-syncd — the daemon
A long-running background service that watches a local folder, reconciles it with Proton Drive, and applies uploads, downloads, moves, and deletes. Event-driven change detection keeps ongoing passes fast.
Proton Drive Sync
Two-way sync between a local folder and Proton Drive — a fast Rust daemon, a scriptable control CLI, and a desktop app that shows you every plan before it runs.
Three ways to drive it
Section titled “Three ways to drive it”proton-sync — the CLI
A thin control client over a Unix socket: check status, pause/resume,
trigger a syncnow, review history, and approve or deny withheld deletions.
Proton Drive Sync — the app
A Tauri desktop app for Linux: live status, an activity ledger, side-by-side conflict resolution, a typed-confirmation dry-run review, settings, onboarding, and a system-tray indicator.
Built to be trusted with your files
Section titled “Built to be trusted with your files”Preview before you commit
Every run can be previewed with --dry-run, which prints the exact plan as JSON
and never touches a byte. The app renders the same plan and gates destructive
applies behind a typed DELETE confirmation.
Deletions ask first
A directional delete-approval guard is on by default: deletions are withheld until you approve them, per item and per direction, and can be relaxed per folder.
Conflicts keep both sides
When both sides change, nothing is lost — the engine writes a .proton-cloud
sidecar so you can resolve it deliberately.
Commit only after success
The sync index records an action only after its side effect succeeds, in incremental checkpoint commits. A failure mid-plan keeps completed work durable and replans the rest; it never leaves half-recorded state.
Where to next
Section titled “Where to next”Install itRequirements, the proton-drive CLI, building from source, and native packages.
Do a first syncPreview a plan, start the daemon, and drive it from the CLI in a few minutes.
Understand the modelThree sources of truth, bootstrap vs. ongoing, and what each action means.
Use the desktop appThe screens, the tray, and how the app maps onto the daemon's real surface.