[REQUEST] - Feature Request: Add Deletion Confirmation Modal for Prompts in Qwen Studio Desktop
起始日期 | Start Date
september, 05, 2026
实现PR | Implementation PR
To implement this feature safely, changes should be introduced across the state management layer and the UI component layer of the desktop application:State Management (Frontend View-Model):Introduce a transient UI state variable isDeleteModalOpen: boolean within the prompt workspace controller.Interactions that trigger a deletion should switch isDeleteModalOpen to true and cache the target prompt ID in a temporary variable (promptIdPendingDeletion), rather than immediately dispatching the destructive action to the global store.UI Component Layer:Create a reusable component wrapping standard desktop design tokens (matching Qwen Studio's theme).Bind the onConfirm property of the modal to the actual deletion dispatch function: dispatch(deletePrompt(promptIdPendingDeletion)).Bind the onCancel or onClose property to a function that resets both isDeleteModalOpen to false and clears the temporary ID.
相关Issues | Reference Issues
Closes / Related to: # (Leave blank or insert relevant issue number if tracking an existing UX discussion regarding prompt persistence) See also: Feature requests regarding "Prompt History" or "Local Workspace Auto-Save."
摘要 | Summary
When working within the desktop version of Qwen Studio, users can accidentally delete a prompt they are working on with a single click or keystroke. Once deleted, the prompt is permanently lost, forcing the user to manually rewrite it from scratch. This proposal requests the implementation of a confirmation modal box (or an "Undo" toast notification) before a prompt is permanently purged from the interface, preventing accidental data loss and improving the overall user experience.
基本示例 | Basic Example
Current Behavior:User spends 15 minutes drafting a complex system prompt.User accidentally clicks the "Delete" icon or presses a destructive hotkey.The prompt is instantly wiped from the workspace with no way to recover it.Proposed Behavior:User clicks the "Delete" icon on a prompt.A modal dialog overlays the screen: Delete Prompt? Are you sure you want to delete this prompt? This action cannot be undone. [ Cancel ] [ Delete ] If the user clicks Cancel, the workspace state is preserved. If they click Delete, the prompt is removed.(Alternatively, an "Undo" toast banner pops up at the bottom of the screen for 5 seconds post-deletion).
缺陷 | Drawbacks
Added Friction: Users who intentionally want to clear out prompts quickly will now have to click twice instead of once, which might slow down power users.UI Clutter: Adding a modal introduces an extra UI asset that needs to be maintained, localized, and tested across different desktop window scaling sizes.
未解决问题 | Unresolved questions
Global Toggle: Should we include a checkbox inside the modal that says "Don't show this warning again", allowing users to opt out of the confirmation friction? If so, where should that setting live in the app preferences?Alternative Approaches: Would a non-intrusive "Undo" toast notification (similar to Gmail's delete mechanic) be a cleaner UX pattern than a hard stop modal?
Source: QwenLM/Qwen