🌐 English · Deutsch · 简体中文 · Italiano · Español · Français · 日本語 · Português · Русский
Unofficial Linux desktop bridge for Proton Drive using Proton's official proton-drive CLI.
Not affiliated with, endorsed by, or sponsored by Proton AG.
Version 0.3.6 - Reliable sync, transfer queue, conflict recovery, and signed updates.
Aux Proton Drive Bridge gives Linux users a GUI for Proton Drive operations through Proton's official CLI. It includes persistent sync metadata, bidirectional sync, a live transfer queue, conflict management, and signed updates.
GitHub release:
https://github.com/Auxillo-Tech/Aux-Proton-Drive-Bridge/releases/latest
Release assets include:
- AppImage for broad Linux compatibility
.debfor Debian/Ubuntu/Mint/Pop!_OS-family systems.rpmfor Fedora/RHEL/openSUSE-family systems- source archives
SHA256SUMS.txtrelease-manifest.json- required Ed25519 signature (
SHA256SUMS.txt.sig)
- Sync metadata DB - SQLite-backed tracking of every tracked file's local and remote state
- Live transfer queue - Concurrent transfers with priority, pause/resume, cancel, retry
- Progress parser - Real-time parsing of proton-drive CLI output for transfer progress
- Conflict detection & resolution - Detects LOCAL_REMOTE_MODIFY, LOCAL_DELETE_REMOTE_MODIFY, TYPE_MISMATCH, HASH_MISMATCH conflicts with resolution strategies
- Bidirectional sync engine - Local filesystem watching via fs.watch + remote polling via CLI
- Sync modes - Conservative (upload-only, skip existing), One-way upload, One-way download, Bidirectional
- Auto-updater - GitHub Releases-based update checking and download
- Release signing - GPG and signify/minisign signing scripts
- File manager integration - Nautilus, Dolphin, Thunar context menu scripts
- Automatic recovery - Resume large transfer sets, reconcile byte-identical legacy conflicts, and continue batches without waiting for the next poll
- Tabbed UI - Separate tabs for Files, Sync Dashboard, Conflicts, Queue, and Updates
- Detects the installed Proton Drive CLI
- Opens Proton browser login via
proton-drive auth login - Lists
/my-files - Downloads selected files/folders
- Downloads all visible
/my-filesentries - Uploads local files/folders to
/my-files - Lets the user choose a local destination folder
- Opens the local download folder
- Shows activity logs and persistent transfer history
- Serializes Proton CLI operations to reduce SQLite cache-lock conflicts
- Keeps Proton authentication in Proton CLI's configured OS secret store
- One-way backup profile with scheduler (30 min)
- System tray with quick actions
- Background close-to-tray mode
Downloads use:
- folder conflict strategy:
merge - file conflict strategy:
skip
Existing local files should not be overwritten by default.
- Linux x64
- Proton Drive CLI available as
proton-drive - A Proton account
- Browser access for Proton login
- Linux secret store supported by Proton CLI, such as KWallet, GNOME Keyring/libsecret, or
pass
The installed CLI owns authentication. The bridge supports one active Proton account/session at a time; saved backup settings do not create separate authentication contexts.
Download and run:
Aux.Proton.Drive.Bridge-0.3.6-x86_64.AppImage
Make it executable and run it from your file manager or terminal.
Download:
Aux.Proton.Drive.Bridge-0.3.6-amd64.deb
Install with your graphical package installer or with apt/dpkg.
Download:
Aux.Proton.Drive.Bridge-0.3.6-x86_64.rpm
Install with your graphical package installer, dnf, zypper, or rpm.
See full instructions: docs/INSTALL.md.
- Install Proton Drive CLI and confirm
proton-drive versionworks. - Launch Aux Proton Drive Bridge.
- Click Sign in.
- Complete Proton login in the browser.
- Click Refresh files.
- Select files/folders from
/my-files. - Pick the local destination folder.
- Click Download selected, Download everything, or Upload files/folders.
- Check the Sync tab to start background sync.
- View Conflicts tab to resolve any detected conflicts.
Sync never propagates deletion. It restores or preserves the surviving copy according to the selected direction instead of deleting cloud or local data. Skipped transfers remain unresolved and are shown as conflicts.
See full usage guide: docs/USAGE.md.
docs/INSTALL.md- install instructions by distro familydocs/USAGE.md- sign-in, list, download, upload, sync, workflowdocs/TROUBLESHOOTING.md- common Linux/CLI/keyring problemsdocs/SECURITY.md- credential handling and app security modeldocs/RELEASE_STATUS.md- current release state and limitations
npm ci
npm run check
npm startBuild local release artifacts:
npm run check
npm run dist:linux # Build AppImage, .deb, .rpm on LinuxRelease outputs are written to dist/.
Key points:
- Aux Proton Drive Bridge never asks for your Proton password.
- Authentication is delegated to Proton's official CLI/browser flow.
- Renderer
nodeIntegrationis disabled. - Electron context isolation is enabled.
- CLI calls are executed as argv arrays, not shell strings.
- Credentials and tokens are redacted from logs and stored data.
See docs/SECURITY.md.
Implemented foundations:
- Sync metadata DB (SQLite)
- Live transfer queue
- Progress parser
- Conflict system
- Bidirectional sync
- Auto-update via GitHub Releases
- Signing/attestation scripts
- File manager integration
- Automatic AMD Navi 48 software-rendering fallback on affected Linux systems
- Desktop notifications
- Conflict review UI with metadata diff viewer
- AUR packaging - PKGBUILD available in
dist/aur/ - Flatpak packaging - not shipped until a sandboxed Proton CLI integration is validated
- Wider distro qualification
- Desktop notifications for all events
- Advanced conflict diff viewer with content comparison
- Multi-account simultaneous sync
Aux Proton Drive Bridge is free and open source. If it helps your workflow, you can buy me a coffee.