Self-hosted backups, recovery, and updates

Use these controls only for an instance you operate. Hosted runtime updates and operational backups are managed outside the customer settings surface.

Backups

Open Settings → Backups. Configure automatic snapshots and incremental exports, then review retention for daily, weekly, and monthly copies. Use Export or Snapshot for a manual copy. Check the resulting archive rather than assuming a scheduled backup ran.

Restore drills

Verify a restore restores into a temporary location and checks the result without replacing live data. A monthly restore drill can make this a routine. Review failed drills promptly: an archive existing does not prove it is usable.

Time travel

Local edit history can record configuration, skills, prompts, project context, and memory notes. Filter for changes made by unattended work when investigating overnight behavior. Preview the selected changes and affected files before restoring. This is separate from conversation rewind and Chat file checkpoints.

Sync

Enable sync only when you want another machine to share changes through storage you control. Choose a configured transport, pull interval, and shard encryption policy. Review conflicts using the local value, remote value, and drafted merge; do not assume a proposed merge is already applied.

Updates

Open Settings → Updates to inspect version information, check updates, and read the changelog. Automatic updates and developer branch tracking are distinct modes. Apps update individually through their own management surface.

The project is pre-1.0. Keep a verified recovery path before changing runtime versions, and confirm release sources rather than assuming a published distribution exists.