How to vibe codeIDrive

Prerequisites

• Node.jsfree

  Required for running the web dashboard and CLI build tools.

• GitHubfree

  Source code repository and version control.

• Rust / Cargofree

  Required for building efficient cross-platform client-side file monitoring tools using Tauri.

AI coding tools

• Claude Code

  Best-in-class terminal agent for scaffolding file-watching codebases and setting up complex background daemons.

• Cursor

  Ideal AI code editor for inspecting multi-file Tauri and TypeScript codebases.

Build guide

1. 01Project Scaffolding & Database Schema

   Initialize a Next.js full-stack repository with Turso and better-auth, establishing database tables for user accounts, registered devices, backup job statuses, and file chunk manifests.

   Scaffold a new Next.js application using TypeScript and Tailwind CSS. Integrate Turso as the SQLite database provider and configure better-auth for secure user authentication (email/password and session management). Create database migrations and schema models for users, devices (storing OS type, hostname, and last-seen timestamp), backup_jobs (tracking file paths, total size, status, and progress), and file_manifests (mapping original file paths to chunk hashes stored in S3/B2). Ensure all environment variables are cleanly separated in a .env.example file. Write automated tests for the auth and device registration routes using Vitest, and verify that user sessions persist correctly across page reloads before proceeding.

   ⧉copy promptopen in Claude CodeCopen in Codexopen in Cursor

2. 02Client Desktop Daemon Setup with Tauri

   Build a lightweight desktop wrapper using Tauri and Rust to monitor local file paths and communicate with the backend dashboard.

   Initialize a Tauri v2 desktop application workspace inside the project repository, configured with a React/TypeScript frontend shell. Implement a Rust-based system tray utility and a background daemon process that starts automatically upon user login. The background service must expose local IPC commands to register the local machine UUID with the central Next.js backend via authenticated API endpoints. Set up robust error logging in Rust to catch file permission denied errors and disk access exceptions gracefully without crashing the background service. Verify that the Tauri build compiles successfully for both macOS and Windows targets.

   ⧉copy promptopen in Claude CodeCopen in Codexopen in Cursor

3. 03File System Watcher & Incremental Chunking Engine

   Implement recursive directory traversal and file change monitoring using Rust notify crates, splitting files into cryptographic blocks for efficient backup.

   Implement a file system monitoring engine inside the Tauri Rust core using the 'notify' crate to watch designated user folders in near real-time. When a file is modified or created, the engine must compute SHA-256 rolling checksums and split the file into fixed-size binary chunks (e.g., 4MB blocks) to enable block-level incremental backups. Build a local SQLite metadata cache on the client machine to track which file chunks have already been uploaded successfully to prevent redundant network transfers. Ensure the engine respects user-defined exclusion patterns (e.g., node_modules, cache files) and handles locked files cleanly by catching IO sharing violations.

   ⧉copy promptopen in Claude CodeCopen in Codexopen in Cursor

4. 04Client-Side Encryption & S3-Compatible Upload Pipeline

   Add zero-knowledge AES-256 client-side encryption to file chunks before uploading them to Backblaze B2 object storage.

   Implement a zero-knowledge cryptographic encryption module in the Rust desktop client using AES-256-GCM. Derive an encryption key from a user-supplied private passphrase using PBKDF2 with a high iteration count, ensuring the raw encryption key never leaves the client device or touches the cloud backend. Before uploading any file chunk to Backblaze B2, encrypt its binary payload locally and generate a secure HMAC tag. Write an asynchronous upload worker queue in Rust that streams encrypted chunks to Backblaze B2 via S3-compatible APIs with automatic exponential backoff retry logic for transient network failures.

   ⧉copy promptopen in Claude CodeCopen in Codexopen in Cursor

5. 05Centralized Web Dashboard & Remote Device Management

   Build the web control panel interface to monitor backup health, view device statuses, and trigger remote restore operations.

   Build a responsive web dashboard using Next.js and Tailwind CSS that displays all registered user devices, their online/offline health status, last backup timestamps, and total storage utilization graphs. Implement server actions to fetch backup logs and job metrics from the Turso database. Add a file browser view that queries the file_manifests table, allowing users to select historical file versions (supporting up to 30 point-in-time versions) and request remote file restores. Include real-time status indicators reflecting active backup jobs reported by client daemons.

   ⧉copy promptopen in Claude CodeCopen in Codexopen in Cursor

6. 06Versioning, Archiving, and End-to-End Verification

   Implement snapshot retention rules, true archiving logic (preventing automatic cloud deletion when local files are removed), and end-to-end integration tests.

   Implement snapshot versioning and archive cleanup logic in the backend API. Ensure that when files are deleted locally, they are retained in the cloud archive unless an explicit 'Archive Cleanup' routine or manual purge is executed by the user. Write comprehensive end-to-end integration tests simulating a full backup cycle: file creation, local chunking, client-side encryption, S3 upload to Backblaze B2, historical version logging, and a complete file restoration workflow downloading and decrypting chunks back to disk. Verify all edge cases including network disconnection mid-backup and resuming partial uploads.

   ⧉copy promptopen in Claude CodeCopen in Codexopen in Cursor

Cost vs paying for IDrive