https://github.com/OpenHands/agent-canvas/pull/739 - This is a design review/update with some new concepts for Customizations and Automations. Posting here for feedback and review. Please try out the branch yourself. Across all pages, modules: • Unify how modules appear across all pages. Now they have a title, metadata area, and description, with area below for more metadata including pilled information. All modules follow this pattern. • Introducing a new "+" button across all with hover states to remove or disable. Why? Because disabling is not as common as adding. So the UI is optimized around adding. This is also consistent with what I've found across other competing products. • All modules have a two column layout and now properly collapse into a single column at smaller sizes. However, in automations we also have a table/list view added (which is consistent with competing products) • All modules will open a modal, so Skills now have a modal with more data and behave like other modules across mcp and automations. Skills specific: • I've added a Use Skill button in the modal, it will pre-populate a new conversation with the /command for that skill. It still needs some logic so that it doesn't show for skills that are passive. This is meant as a stub UI interaction for a feature I think we're missing. I wanted to demonstrate it on the branch for people to review. @millions-afternoon-47582 can you review this? I think it's close to being complete. Automations specific: • I have a version of the recommended automation templates that follows the universal design pattern. However I have some questions about some of the metadata we're including such as the "time to setup" which seems uncommon and not necessary? It also appears like a some kind of cron job config at first glance. • The modules are now two columns like other pages (and other apps). • The How-to gets put into the button-launched modal that contains instructions. Those instructions still appear when user has no automations setup. • User can run now easily, but toggling on/off is now in the dropdown to clean UI (this is also consistent with conventions I'm seeing) • In a future upgrade to New Automations we can open a modal that the user adds the first prompt to kick of the conversation (Codex does this). Please kick the tires. @millions-afternoon-47582 @hundreds-twilight-32833 @wooden-umbrella-84098 @wooden-umbrella-84098 I updated the New Automation modal. Ultimately I'd like to get this further along to be an actual text input with some templates easily accessible to build the automation.

I will review this pull request and resolve the merge conflicts. Thank you very much! thankyou