workspace-sync

Automate workspace file backups to remote R2 storage with selective exclusions.

Updated Feb 2, 2026

Search Tags:#automation #workspace #backup #sync #r2 #container

Ready to run

npx skills add https://github.com/jerryfane/openclaw-container-tools --skill workspace-sync-jerryfane

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workspace-sync
Source: https://github.com/jerryfane/openclaw-container-tools/tree/main
Command: npx skills add https://github.com/jerryfane/openclaw-container-tools --skill workspace-sync-jerryfane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of manually backing up and syncing workspace files, reducing the risk of data loss during container restarts.

Core Features & Use Cases

Automated Workspace Backup: Syncs local workspace files to R2 storage, ensuring data persistence across container cycles.
Selective Exclusions: Automatically skips large, unnecessary files like node_modules, .git, and build outputs to optimize sync performance.
Use Case: Developers working on OpenClaw projects can run this script periodically to maintain an up-to-date backup, allowing quick restoration if the container is reset.

Quick Start

Run the sync script inside your container to back up your workspace files to R2 and keep a safe, retrievable copy.

Frequently Asked Questions about workspace-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate workspace backups to R2 storage?▼

You can automate workspace backups to R2 storage by running a sync script inside your container, which periodically copies your files to remote R2 storage to prevent data loss during container restarts.

Why do I lose my workspace files when my container restarts?▼

Container restarts reset the environment and erase non-persistent data. Syncing your workspace files to remote R2 storage ensures you maintain an up-to-date, retrievable backup for quick restoration.

Can I exclude node_modules and build outputs from my workspace sync?▼

Yes, the automated workspace sync selectively excludes large, unnecessary files like node_modules, .git, and build outputs to optimize sync performance and enhance efficiency.

What is the best way to keep my development workspace safe in a container?▼

The best way to keep your workspace safe is to run an automated sync script that periodically backs up your local files to R2 storage, ensuring data persistence across container cycles.

Does the R2 backup script work for complex development environments?▼

Yes, the R2 backup script is suitable for developers managing complex or critical environments that require consistent backups and quick restoration if the container is reset.