Desktop: Reset data recovery + crash issue template#965
Merged
Conversation
A failed migration or corrupt SQLite makes the sidecar fail to start forever — updating can't fix it. Reset moves the data dir aside (never deletes) into ~/.executor/backups/<stamp>/ and starts fresh, so the user's connections and secrets stay recoverable. - resetExecutorState() backs up data.db (+ wal/shm) and server-control - Offered two ways: a 'Reset data' link on the in-window crash screen (for crashes under a live window) and a 'Reset data and retry…' button on the fatal-startup dialog (for boot failures), each behind a native confirm - New e2e scenario: corrupts data.db, confirms restart alone fails, then resets and asserts the app heals AND the corrupted db is preserved in the backup dir
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-marketing | a13587f | Commit Preview URL Branch Preview URL |
Jun 12 2026, 04:55 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
executor-cloud | a13587f | Jun 12 2026, 04:55 AM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
The crash-screen reset copy now says what reset is FOR (clears a damaged database) rather than dwelling on the backup. After a reset completes, an info dialog names the exact backup folder and offers Show in folder — so 'your data is backed up' is something the user can act on, not just a promise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #961. Gives users on hard-crashed states a way out, and makes new crash reports easier to triage.
~/.executor/backups/<stamp>/— never deleted — and the app starts fresh. Offered on the in-window crash screen (link) and the fatal-startup dialog (button), each behind a native confirm..github/ISSUE_TEMPLATE/desktop-crash.yml): asks for version, OS, when it crashes, and the diagnostics zip / log file.The damaged-db → reset → healed flow, recorded by the e2e scenario (corrupted bytes verified preserved in the backup):