claude-code - 💡(How to fix) Fix [FEATURE] Execution confirmation prompts block user input - suggest non-blocking UI design [1 comments, 2 participants]

TL;DR

Implement a dedicated UI area for execution confirmation requests to prevent blocking the main input field.

Guidance

• Separate the execution confirmation requests into a non-overlapping UI element, such as a sidebar or popup, to allow users to continue typing in the main input area.
• Implement a focus-shifting mechanism, like up/down arrows, to enable users to switch between the main input area and the confirmation area.
• Ensure that submitting a yes/no answer in the confirmation area automatically returns focus to the main input area.
• Consider adding a visual cue to indicate when a confirmation request is pending, to prevent users from unintentionally ignoring it.

Example

No specific code example can be provided without knowing the implementation details, but a possible approach could involve using a separate HTML element for the confirmation prompt and managing focus programmatically.

Notes

The proposed solution requires changes to the UI and interaction model, which may involve significant development and testing efforts. It's essential to consider accessibility and usability implications when designing the new UI element and focus-shifting mechanism.

Recommendation

Apply workaround: Implement a dedicated UI area for execution confirmation requests, as this approach addresses the core issue of blocking the main input field and allows for a more flexible interaction model.