The idea is:
Add a confirmation step before a node is permanently deleted from the canvas.
Right now, a node can be removed immediately with a single Delete key press. I’d like to suggest a safer delete flow, for example:
Press Delete once to trigger a confirmation state
Press Enter to confirm deletion
Press Escape or click away to cancel
This could also be implemented as an optional editor setting, so users who prefer the current fast behavior can keep it, while others can enable a safer mode for daily workflow building.
My use case:
When building long or complex workflows, it is very easy to accidentally delete a node while editing quickly. In real usage, this often happens when trying to remove text, rename something, or simply move fast across the canvas, and the selected node gets deleted unintentionally instead.
Even if undo exists, accidental deletion still breaks focus, interrupts the building process, and becomes frustrating when working with large flows that contain many connected nodes.
I think it would be beneficial to add this because:
This would reduce accidental destructive actions in the editor and make the workflow-building experience feel much safer and more stable.
For users working on large production workflows, small mistakes like unintended node deletion can slow down iteration and create unnecessary friction. A lightweight confirmation step would improve confidence during editing without changing the core workflow-building experience too much.
Any resources to support this?
There has already been community discussion around accidental node deletion and the need for safer recovery behavior, including requests for better undo support after deleting nodes.
This request is related, but focuses earlier in the interaction flow: preventing accidental deletion before it happens, instead of only relying on recovery after the node is already gone.
Are you willing to work on this?
At the moment, I’m mainly sharing this as a product and UX suggestion based on practical usage. I’d be happy to clarify the use case further, provide examples, or help test the behavior if the team considers it.