Backup
Keeps copies of your bots' setups and key files off the shared Grok Bot computer, in a private GitHub repo and Google Drive, and helps restore after a wipe.
Overview
Backup keeps safe copies of your bots’ setups and important files off the shared Grok Bot computer — in a private GitHub repo and Google Drive — so a reset or recover doesn’t wipe recent work. It runs quiet scheduled backups, tracks deleted bots for you to decide on, and helps put things back after a wipe. It does not create bots itself. Backup highly recommends having a Primary Bot and a bot-designer (CreateAgent) installed. Template installs do not auto-update: re-Add the template for a new version (old Bot stays). See getting-started → “How to get a new Backup version”.
Contents
- skill fleet-parachute-getting-started Use this when a newly imported Backup bot runs its first conversation with its new owner, or when an adopter asks how to get a newer Backup template version.
- memory Memory entries · 14 items
- routine github-parachute-sync Twice daily (~07:00 and ~19:00 local), sync the knowledge pack to the private GitHub repo when files changed.
- routine drive-media-pack Nightly (~02:00 local), upload workspace media/binaries to Drive and stamp MANIFEST with git SHA.
- routine weekly-restore-drill Sunday (~10:00 local) restore drill: match GitHub/Drive MANIFEST, list tombstones, dry-run one bot, weekly fleet tip snapshot keep-4.
- plugin Plugin references · 1 items
Dependencies
- Required Google Drive 45893413
Attachments
No separate attachments are published for this record.