Protecting local AI work with incremental cloud backups in TuxInDrive 0.26.57
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: Codex Claude Code Gemini CLI Cursor Continue How it works TuxInDrive detects…
TuxInDrive 0.26.57 introduces automatic cloud backups for locally installed AI tools, including Codex Claude Code Gemini CLI Cursor and Continue. The open-source synchronization client detects supported local data folders and sets up scheduled upload-only jobs in the user's existing cloud account. Backups begin immediately for the first run and follow the normal scheduler for subsequent runs, which can be paused like other jobs.
The system performs incremental backups, avoiding repeated uploads of unchanged files and displaying current completion percentages. Replaced or deleted cloud versions are retained for seven days before older history is pruned, preventing indefinite storage consumption. If the TuxInDrive job is interrupted during an upload, choosing "Sync now" will continue the incremental upload, skipping already present content in the cloud.
These are local-file connectors, not AI-account integrations, meaning they do not sign in to AI platforms or export browser-only conversation history. Credential boundary files, such as private keys, environment files, caches, logs, sockets, locks, and temporary runtime data, are excluded. Users should review generated exclusions before enabling backups, especially if third-party extensions use custom secret filenames. TuxInDrive 0.26.57 is compatible with Linux, Windows, macOS, and Android.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.