clawdbot-skill-update

Automating multi-agent Clawdbot backups involves reading agent workspaces from clawdbot.json and preserving each workspace state. This Skill discovers dynamic workspaces and backs up each agent configuration in a single consistent operation.

Yes, you can run a dry-run preview before updating your Clawdbot production environment. The dry-run validates the backup state and previews changes, allowing you to execute the full backup and update safely with rollback support.

Yes, this backup and update workflow captures git state for Clawdbot workspaces. It records the git state alongside dynamic workspace configurations to ensure comprehensive validation and safe rollback options during production updates.

You need bash, jq, tar, git, and bc installed to perform Clawdbot restore and rollback operations. These dependencies handle workspace discovery, state capture, archiving, and validation logic required for the automated restore workflows.

The best way to restore a multi-agent Clawdbot setup after a failed update is using the built-in rollback option. It leverages the captured git state and workspace backups to safely revert all agents to their previous consistent state.

You should avoid automated updates for multi-agent Clawdbot deployments when dynamic workspace discovery cannot read your clawdbot.json, or when the required dependencies like bash, jq, tar, git, and bc are unavailable in your target environment.