What is proton-drive-cli-sync?

Proton Drive CLI Sync is a Linux tool that gives Proton Drive real continuous folder syncing, something the official Proton Drive command line tool does not do on its own. Proton's official CLI can upload files, list them, and check info, but it only performs one off actions and is meant to be called from scripts or scheduled jobs, not run as a background sync engine. This project fills that gap. At its core is a Python engine that wraps the official CLI to behave like a mirror sync, detecting new or changed files instead of blindly re-uploading everything every time it runs. A graphical editor built with Tkinter lets you manage which folders get synced, set per folder exclusions, watch live output, and trigger both cache priming and manual sync runs, each with its own settings and stop controls. On top of that batch engine sits a real-time layer that watches folders for changes using inotify and syncs them immediately through systemd background services, with the older scheduled batch running weekly as a backup safety net rather than the primary method. A NAS, network attached storage device, is entirely optional. Fresh installs start in local only mode, syncing straight to Proton Drive with no NAS involved. If you do add one and it becomes unreachable, for example after a reboot or network drop, the tool pauses only the NAS related folders while local folders keep syncing normally, then resumes automatically once the NAS reconnects, without losing any changes. Other features include a self test that checks NAS folder paths are set up correctly with color coded status indicators, an upload progress indicator during syncs, copy to clipboard buttons for shell commands shown in the app, and a warning badge that flags when a NAS deployment is still pending without taking any action on its own. The tool depends on a specific tested version of Proton's official CLI, warns you if a different version is installed, and stores login credentials through the system's secret storage service. It also supports two separate accounts syncing at once by running under two different Linux user sessions on the same machine, each with its own lock file and cache so they never interfere with each other. The full README is longer than what was shown.