Getting Started
Uninstalling and resetting Foxora
Uninstalling the app and resetting a preference are different actions; neither should be treated as deletion of your projects or cloud account.
View MarkdownPublished Studio guide. Some screenshots show earlier versions.

Steps
- Export any data you need from Settings → Data and copy important project files elsewhere.
- Close running tasks and terminals, then quit Foxora.
- Remove Foxora through the normal macOS or Windows application-removal flow.
- If you only need a fresh look or setup checklist, use Reset appearance or Reset onboarding in Settings → System instead.
Expected result
The application is removed, or the chosen local preference is reset, without silently deleting folders you created outside Foxora.
Note: Account and cloud-data deletion are separate from uninstalling. Confirm their status before removing any local backup.
Explicit recovery options
Quit Studio, including its tray process. Run as your usual desktop user, without sudo. Normal install and update commands never run recovery.
- Check: reports whether local state exists without reading project contents or changing files. The installer downloads the checksum-pinned script; the check itself sends no local data.
- Sign-in: backs up the device session. macOS and Windows select a new production sign-in profile and preserve old OS-vault credentials. Linux backs up the app webview profile, also resetting preferences and recent folders. Close old login tabs and start one new attempt.
- View: backs up the app webview profile and resets UI preferences; on Linux it also signs out. This may not remove entries restored from existing tasks. Project databases, project files, packs and ordinary browser profiles stay in place.
Choose a recovery action and copy its command. These actions cannot patch compiled OAuth or duplicate-row handling, and do not guarantee a PKCE fix.
Private backups and undo
Repairs print a backup path under your Foxora data folder’s recovery directory. Never upload it. To undo, quit Studio and preserve any newly created state separately. Restore items to the original paths in moves.tsv (macOS/Linux) or moves.json (Windows). If new-marker.txt exists, move its named pointer aside before restoring auth-generation, if present. Keep your own backup of important project folders.