Skip to content

Project Backup

Upload an entire project directory to Tusky for durable, decentralized backup. Files are encrypted client-side and sync to the Walrus network automatically — no single point of failure.

  • MCP server configured and connected to your agent
  • For private vaults: TUSKYDP_PASSWORD set in the MCP config

Tools used: tusky_vault_create, tusky_folder_create, tusky_file_upload

tusky_vault_create({ name: "myapp-backup-2025-03-16", visibility: "private" })

Create folders that match your project layout:

tusky_folder_create({ vaultId: "<vault-id>", name: "src" })
tusky_folder_create({ vaultId: "<vault-id>", name: "components", parentId: "<src-folder-id>" })
tusky_folder_create({ vaultId: "<vault-id>", name: "tests" })

Upload files to the corresponding folders:

tusky_file_upload({
filePath: "/path/to/project/src/index.ts",
vaultId: "<vault-id>",
folderId: "<src-folder-id>"
})

Repeat for all files. The agent can walk the directory tree and upload in bulk.

Files start in hot status and sync to Walrus in the background. No action needed — the sync happens automatically.

  • Periodic backups of source code or configuration
  • Snapshotting a project before a major refactor
  • Archiving build artifacts or release bundles
  • Creating a durable record of a project state at a point in time
  • Use dated vault names (e.g., myapp-backup-2025-03-16) to distinguish snapshots
  • Skip node_modules and build artifacts — back up source code and configuration, not generated files
  • Use tusky_file_upload for local files — it handles reading from disk, encryption, presigned URLs, and upload confirmation automatically
  • Use folders liberally — they make it easy to navigate the backup later