Backups

Your VM's state is saved automatically and restored whenever you update it. There's nothing to set up.

When you update your agent to a new version, the VM is rebuilt from a fresh image and the old disk is replaced. Just before that happens we snapshot your important data, then restore it on the new VM's first boot. Snapshots also run periodically in the background.

Important

Anything you save outside /workspace — including your home directory (/root) — is not backed up, and is erased on every update. Keep your work in /workspace.

What's preserved

  • Your files in /workspace — the agent's working directory
  • Agent memory and configuration
  • Scheduled jobs (cron)
  • Channel connections — Telegram, Discord, Lark
  • Signed-in browser sessions — e.g. Google

What's not preserved

Anything outside the locations above is reset to the fresh image on every update:

  • Files saved outside /workspace, including your home directory (/root), /tmp, and other system paths
  • Software you install yourself (apt, global npm / pip, and similar)
  • Caches

Keep your work in /workspace. It's the one file location that survives an update. When you SSH in, cd /workspace before creating files.

Files missing after an update?

They were almost certainly saved outside /workspace — most often in your home directory (/root). Only /workspace and agent state carry across an update; everything else is reset to the image.

Move existing work into /workspace (for example mv ~/my-project /workspace/) and it will be preserved from then on. Files saved elsewhere before an update can't be recovered.