clipboard-sync-cross-device

Use pyperclip to monitor clipboard changes, encrypt content with AES-256-GCM via pycryptodome, and upload it to Google Drive or Dropbox. A background thread on the other device polls the cloud file, decrypts it, and writes it to the local clipboard.

Derive a 32-byte key from a shared password using PBKDF2, then encrypt with AES in GCM mode, which provides both confidentiality and integrity verification. The salt, nonce, and authentication tag are prepended to the ciphertext and base64-encoded for storage.

Yes, the implementation supports Google Drive through the google-api-python-client library with OAuth2 credentials, and Dropbox via the dropbox package using an access token. Both providers store the encrypted clipboard payload as a JSON file.

Common causes include invalid or expired cloud credentials, mismatched CLIPBOARD_SYNC_PASSWORD values between devices, and network connectivity issues. Delete token.json to re-run the OAuth flow and verify the encryption password is identical everywhere.

Selective sync supports images and files through configuration flags, with a configurable maximum file size in megabytes. Text syncs by default, while image and file syncing can be toggled in the config.json selective_sync section.

Increase the polling interval from the default 1 second in the monitor loop and the 5 second cloud sync interval. Disabling image and file sync also reduces processing overhead when those content types are not needed.