feat: undo system for destructive actions #93

New issue

Closed

opened 2026-03-25 18:21:52 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-03-25 18:21:52 +00:00

Problem

Destructive actions like dd (delete) and status changes (pp/ww/bb) are permanent with no way to reverse them. The y/N confirmation prompt was removed for speed, so undo is the safety net.

Solution

Client-side delayed execution: destructive actions optimistically update the UI but hold the server action in a timeout (~5s). A minimal undo indicator allows cancelling before the action commits. This avoids schema changes (no soft-delete column needed).

Scope: dd delete, x complete, and status operators.

## Problem Destructive actions like `dd` (delete) and status changes (`pp`/`ww`/`bb`) are permanent with no way to reverse them. The y/N confirmation prompt was removed for speed, so undo is the safety net. ## Solution Client-side delayed execution: destructive actions optimistically update the UI but hold the server action in a timeout (~5s). A minimal undo indicator allows cancelling before the action commits. This avoids schema changes (no soft-delete column needed). Scope: `dd` delete, `x` complete, and status operators.

barrettruth commented

2026-03-29 00:00:59 +00:00

Landed — undo stack with u keybinding