Backup the setup, not the repo
Continuity is a backup of how you work, not a backup of what you wrote. Env profiles, preferred scripts, ports, catalog names. Encrypted on the device before upload. The key is yours. The repo stays in git, on disk, where it already lives.
Cloud dev boxes blur this on purpose: if they hold the source, restore is easy and so is a subpoena. Rig refuses that trade. A new Mac clones from GitHub, then Continuity puts the setup back. You are coding after lunch, not after a migration project.
What is in a snapshot
The shape: which processes, which start order, which env names (values stay in ciphertext). Not /Users/you/Code/client-x. Paths are local on purpose. Teleport and Continuity are cousins; neither is a remote IDE.
What happens when a laptop dies
- Get a Mac. Install Rig.
- Sign in. Restore Continuity.
- Clone the repos you actually need.
- Start the group. MCP link if you use an editor agent.
Guide: Continuity restore on a new Mac, recovery key, what syncs.
Honest limits
If you never commit, Continuity will not invent the missing files. If you want Time Machine for the whole disk, use Time Machine. This product solves "the new machine does not know how I boot the app."