But I'd like to highlight some recent usability concerns with both the web interface and Chrome Extension:

The chat interface is experiencing responsiveness issues where multiple clicks are required to activate the input field 1 . This creates unnecessary friction in the user experience.

A more critical issue is that submitted prompts occasionally disappear completely, requiring users to rewrite their entire input 5 . This data loss is particularly disruptive to workflow efficiency.

Regarding the new interface, while I understand the intention to improve, I've found the older version more user-friendly and stable 1 . I've had to switch back to the old interface to maintain functionality, which suggests there might be some optimization needed in the new design 7 .

Despite these challenges, I recognize Merlin's value as a productivity tool 6 . I believe addressing these interface stability issues, particularly the disappearing text problem and click recognition, would significantly enhance the user experience. The core functionality is excellent, but these technical hurdles are impacting the otherwise smooth operation of the tool.

Would it be possible to:

Improve the input field responsiveness

Implement an auto-save feature for drafts

Review the new interface design with user feedback in mind