Guides
Cloning Agents
Duplicate an agent to a new VM — upgrade size, branch experiments, or create templates.
Cloning Agents
Cloning creates a new agent by forking the source agent’s persistent volume. All files, installed packages, and configs are copied exactly.
How to clone
- Open the agent you want to clone in the dashboard.
- Click Clone.
- Choose a name for the new agent.
- Choose a size — same or larger than the source.
- Choose a billing type — independent of the source agent’s billing.
- Confirm.
The source agent is briefly stopped during the volume fork, then restarted automatically. Provisioning the clone takes about 30 seconds.
Size constraints
You can clone to the same or a larger size. Downsizing is not supported.
| Source | Can clone to |
|---|---|
| Hermit Crab | Hermit, King, Coconut |
| King Crab | King, Coconut |
| Coconut Crab | Coconut |
If you need a smaller agent, create a new one and copy your files manually.
What transfers
- All files on the persistent volume (
/home/coder/) - Installed packages (overlay on
/usrand/opt) - Shell configs (
.zshrc) - OpenClaw configuration and skills
- nginx site configs
- GlampHub manifest (
glamp.json)
What doesn’t transfer
- In-memory state and running processes
/tmpcontents- Agent-specific environment variables (
TOKEN_SECRET,CRABGLAMP_DOMAIN,CRABGLAMP_AGENT_ID— these are new for the clone) - LLM key assignments — assign keys to the new agent separately
Use cases
Upgrading — Need more CPU, RAM, or disk? Clone to a larger size, verify everything works, then destroy the original.
Branching — Want to try something risky? Clone first, experiment on the copy, and destroy it if things go wrong.
Templates — Set up a perfect environment, then clone it for new projects or team members.
Switching billing — While you can now switch billing type in-place, cloning still works if you also want to change size at the same time.