1. The Three Escape Hatches
Accelerated Logic AI prioritizes local-first browser privacy, storing workspace data in client-side IndexedDB. To protect against browser cache purges or machine switches, three distinct escape hatches are provided:
Export Web Sandbox and Python projects to real GitHub repos for Vercel deployment or local git clone workflows.
Background cloud sync using Google's hidden AppDataFolder. Keeps chat histories, skills, and memories synchronized across laptops.
1-click complete JSON database dumps containing all chats, uploaded files, custom skills, memories, and model configs.
2. GitHub Integration & Code Pushing
Push code directly from the Web Sandbox to GitHub using client-side Personal Access Tokens (PAT):
GitHub Push Workflow:
- Open Sidebar → GitHub Integration or click Push to GitHub in Web Sandbox.
- Paste a GitHub PAT with
reposcope. Tokens remain strictly local in browser storage. - Select an existing repository or create a new public/private repository.
- Specify the branch (e.g.
main) and commit message, then click Push Workspace Code.
ZIP Download Alternative: Click Download ZIP in Web Sandbox to download a standalone Vite + React project without requiring API keys.
3. Google Drive AppData Folder Sync
Google Drive sync utilizes the secure AppDataFolder scope. Backup files are hidden from normal Drive UI to prevent accidental modification:
Granular Sync Selectors: Toggle background sync independently for Chats, Files, Projects, Skills, and Memories.
Debounced Auto-Save: Modifications save automatically after a ~1.5-second pause (e.g. sending a message or updating a skill).
Multi-Device Information Score Resolution: When opening the app on a second device, Accelerated Logic evaluates total chats, messages, and character counts to seamlessly merge divergent threads.
4. Local Full System Snapshots & Granular Exports
Open Settings → Export Data Workspace for cold storage backups:
Exports all 8 IndexedDB stores into a single timestamped file for full disaster recovery and workspace migration.
Export or import specific subsets independently: Model Configs & Fallbacks, Conversation History, Custom Agent Skills, or Long-Term Memories.
5. Danger Zone: Purge Browser Workspace
Located in Settings → Local Backup, the Purge All Browser Workspace Data engine resets all local IndexedDB object stores, clears local storage tokens, and logs out active Google Drive sync connections for clean handoffs.
6. Recommended Backup Strategy
Weekly: Export a Full System Snapshot (.json) to external cold storage.
During Development: Enable Google Drive sync for real-time multi-device thread continuity.
Project Completion: Push code directly to GitHub repos for production hosting on Vercel or Netlify.
7. Sync & Export Troubleshooting
Drive Session Expired (401)? Click the yellow Drive warning icon in the header to refresh your OAuth authorization token.
GitHub Push 401 Bad Credentials? Ensure your PAT has the repo scope selected during generation on GitHub.
Snapshot Import Override? If Google Drive Sync is active, disconnect Drive temporarily before importing a cold backup snapshot to prevent cloud auto-restore conflicts.
8. A Restore Drill — From Cold Snapshot to Running Workspace
Backups are unproven until restored. Run this drill once on a spare browser profile so the first real recovery is not a research project:
- Export now: Settings → Backup → export the full snapshot. Note the export timestamp and file size — a 2 KB snapshot for a year of heavy use is a red flag, not a relief.
- Open an incognito/clean profile of the same browser and load the app. The workspace is empty — as it would be on a new machine.
- Import the snapshot from the same Settings → Backup panel. Accept the overwrite prompt (the clean profile has nothing worth keeping).
- Verify the load-bearing slices: open a recent chat, check message history rendered; open Skills and confirm your custom skills exist; open Memory and confirm facts returned; equip a model and send one prompt.
- Disconnect the drill profile from any Drive/GitHub connections you used during testing — a drill must not silently re-point your cloud sync.
- Record the drill date in a note. If the export format has changed since your last snapshot, you have just learned that while stakes were zero.
Expected frictions, by design: API keys do not round-trip in the default export (secrets are stripped), so re-enter keys after a restore — an inconvenience that is also a security property. Chat message text restores; in-flight streaming state does not.
9. What Drive Sync Actually Covers — and What It Never Does
| Slice | Sync behavior | Notes |
|---|---|---|
| Chats | Opt-in per toggle | Most valuable slice; debounced ~1.5s after last edit |
| Files (ingested) | Opt-in per toggle | Largest payloads — mind Drive quota |
| Projects (Web Sandbox / Python) | Opt-in per toggle | Stored in the projects doc (e.g. my_ai_projects.json) |
| Skills / Memories | Opt-in per toggle | Small, high-value; sync early |
| Settings | Mirrored, secrets stripped | API keys are NOT in the readable settings document |
| Provider keys & fallback keys | Separate AES-GCM vault | Ciphertext only; vault key record lives in Drive AppData gated by your Google account; restore fills blank slots — never overwrites a newer local key |
| GitHub PAT / OAuth tokens | Never synced | Re-auth on the new device; that is deliberate |
| Drive token itself | Session-scoped | The token proves identity to Google; it never enters the backup |
Where the vault is concerned, understand the shape: the ciphertext lives in AppData with everything else; the key record also lives in AppData; both are reachable only by the signed-in Google account. Losing access to that Google account loses the vault — your regular Google account recovery is therefore also your key recovery.
10. GitHub Token Hygiene — Scopes, Expiry, Rotation
repo— required to read/push code, create commits and branchesread:user,user:email— identity for the connector UI- Nothing else. No
admin:*, nodelete_repo, no workflow scopes unless you actually dispatch Actions
- Prefer fine-grained PATs scoped to specific repositories over classic all-repo tokens
- Set an expiry (30–90 days) and calendar a rotation; treat the token like a password — it grants full API access to the scoped repos
- If a token leaks: revoke immediately at github.com/settings/tokens, re-issue, re-connect in the app. The app stores it locally only — the leak vector is almost always elsewhere
- On a shared machine, do not connect at all; use ZIP export instead
OAuth (the browser sign-in flow) is preferable to pasting PATs where offered: short-lived session tokens, origin-checked relay, no long-lived secret sitting in the browser. PATs remain the right tool for unattended/headless scenarios and fine-grained repo scoping.
11. Trust but Verify — Signs Your Backup Is Actually Healthy
Green flags:
- Snapshot file size scales with usage — re-export monthly and compare
- A restore drill (Section 8) completed in the last quarter
- Drive header shows
Saved, not a staleSyncing...stuck for hours
Red flags:
- "Sync complete" toasts with zero bytes transferred for weeks
- Export JSON that fails to open, or parses but lacks a
datablock - Restores that come back missing a slice — means that slice was never in the export; check the export selectors
The cheapest insurance policy in this entire guide is one afternoon a quarter: export, restore into a clean profile, spot-check three artifacts, done. Everything else is anecdote.