Add explicit crash recovery and destructive-action confirmations
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reading the project’s persistence and application startup code to find how history and tool state are stored and how shutdown is handled. Then trace the existing history-clearing and window-closing flows. Done means crash recovery, safe fallback behavior, and unsaved-work confirmations meet the acceptance criteria, with tests and documentation covering recovery and retention.
Written by the indexing model from the issue text.
Description
Remaining scope (2026-11-06)
P1 usability/reliability. New/Open and ordinary quit already protect unsaved temporary work; saved-project quit acknowledges workspace commits/flushes and offers recovery choices on failure. #149 and #134 are completed. Do not duplicate those flows. This issue is crash detection/recovery and remaining destructive-action confirmations, not automatic reopening of recent projects (#152).
Temporary RAM-only content cannot be recovered after forced termination. A saved file's committed contents are not a guarantee that every in-flight edit survived. See docs/project-exit-guarantees.md.
Acceptance criteria
- Detect unclean shutdown without false warnings after a clean exit.
- Offer explicit recovery of committed saved-project state, never silent startup reopening or replacement of a potentially recoverable file.
- Provide safe inspection/read-only or copy-based recovery and actionable errors for corrupt, incompatible, locked, or missing files.
- Define confirmations before destructive actions such as clearing history; preserve cancel behavior and document what is irrecoverable.
- Deterministic crash/reopen tests cover marker cleanup, committed versus in-flight state, failures and safe fallbacks.
- Update Safety, Workbench and exit guarantees; record a manual recovery/confirmation check.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 137
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from andyintheshell/perseid
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
andyintheshell/perseid#73 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation focus: pro parity priority: p3
Difficulty 5/5 Over a week Newbie friendliness 35/100
andyintheshell/perseid#192 ·
Maintainers usually reply within 1 day
-
enhancement focus: collaborator priority: p0
Difficulty 5/5 Over a week Newbie friendliness 25/100
andyintheshell/perseid#191 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement focus: community parity focus: usability priority: p2
Difficulty 5/5 Over a week Newbie friendliness 45/100
andyintheshell/perseid#179 ·
Maintainers usually reply within 1 day
-
enhancement focus: community parity focus: usability priority: p2
Difficulty 5/5 Over a week Newbie friendliness 35/100
andyintheshell/perseid#178 ·
Maintainers usually reply within 1 day
All issues in andyintheshell/perseid
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aaif-goose/goose#13364 ·
Maintainers usually reply within 1 day
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ClickHouse/ClickHouse#130006 ·
Maintainers usually reply within 1 day
-
[Bug]: PostgreSQL backend: Queue.remove() / Job.remove() never emit the QueueEvents "removed" eventPossibly taken @1AbdullahButt claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
taskforcesh/bullmq#5085 ·
Maintainers usually reply within 1 day