AI-assisted work increasingly depends on local state that does not live in a normal project repository: conversations, prompts, memories, skills, commands, and tool configuration.
I maintain TuxInDrive, an open-source multi-cloud synchronization client. Version 0.26.57 adds automatic cloud backups for locally installed:
TuxInDrive detects supported local data folders and creates scheduled, upload-only jobs in a cloud account you already control. The first backup starts immediately; later runs use the normal scheduler and can be d like other jobs.
Backups are incremental. Unchanged files are not uploaded again, and the job displays its current completion percentage while running. Replaced or deleted cloud versions are retained for seven days, then older history is pruned after a successful run so storage consumption cannot grow indefinitely.
If TuxInDrive closes during an upload, the job records an interrupted state. Choosing Sync now safely continues the incremental upload and skips content already present in the cloud. These are local-file connectors, not AI-account integrations. They do not sign in to Codex, Claude, Gemini, Cursor, or Continue, and they cannot export browser-only conversation history.
Known authentication files, private keys, environment files, caches, logs, sockets, locks, and temporary runtime data are excluded. Because third-party extensions may use custom secret filenames, users should still review the generated exclusions before enabling a backup.
TuxInDrive 0.26.57 is available for Linux, Windows, macOS, and Android:
The project is open source. Feedback on additional local AI tools, exclusion rules, and restore workflows is welcome.