Quick Resurrection

Problem

Once an AI agent has accumulated identity files, workspace state, tool credentials, subagents, and cron jobs, moving it to a new machine or reinstalling the system is not just copying files. agentId, cwd, and allowAgents together determine whether subagents can read the correct SOUL.md, stay isolated in their workspace, and be allowed to spawn. If only identity files are packed while workspace paths, cron jobs, or agent allowlists are missed, the migrated agent can fail with agentId is not allowed, load the wrong SOUL.md, or become temporarily unavailable after a Gateway restart.

How It Works

Quick Resurrection splits migration into two reviewable steps: run pack.py in the old environment to create a migration bundle, then run migrate.py in the new environment to restore it. It infers the active workspace, collects SOUL, MEMORY, TOOLS, team members, skills, and cron configuration, and creates a backup under ~/.qclaw/backup/ before restoring. During migration, it asks how to handle the main agent, copies identity files, team members, and skills, merges agents and hooks.allowedAgentIds in openclaw.json, then creates cron jobs and restarts the Gateway. --dry-run shows the diff, while --no-cron and --no-restart can skip sensitive actions.

Boundaries And Caveats

The migration bundle may contain sensitive material such as API keys, credentials, or server addresses, so it should not be shared publicly and should be transferred using encrypted media. If the bundle source is uncertain, audit pack.py and migrate.py line by line first, or test in an isolated environment. After migration, still verify workspace paths, backup directories, cron payloads, and the agentId + cwd required for subagent spawning.