Hey @hundreds-twilight-32833, if you or @breezy-kilobyte-39430 have any additional feedback on github.com/OpenHands/OpenHands/issues/16236 or would like to add some before @millions-afternoon-47582 starts on it this week please feel free! I think that if we’re aligned on the high level that having an automations dashboard on the front page is a good thing then we can probably go ahead with the impl and improve the design during the PR review process. But if you think that directionally it might be off, then I think we can also pause until we’re aligned on the direction.

Hello everyone, I have created a pull request for the issue. • feat: ship the featured automations landing dashboard Thank you very much! thankyou

Awesome, thank you! I think my biggest question is how we can display the result of the automation (e.g. the last message from the user) within the dashboard. Ideally we’d be able to browse the actual results of the agent run from a single page without clicking through as well. I wonder if we could test this on the oss team VM and see what it looks like when we have actual automations runs populated. cc @modern-fireman-99755 in case you’d need to help Hiep get access.

i think you could install your branch of the agent-canvas in the VM and we can test it

Yes, there have been no agent-server changes so far.

Yeah, I think so. But I’m not sure if Hiep has ssh access for the VM. But yeah, a DM is a good place to share the info

I'm going to chat with @breezy-kilobyte-39430 in ~hour to talk through this a bit too. We'll have some feedback before EOD

SGTM, thanks! Let’s set up testing of the current version on the oss vm, and when we get feedback we can test the revised version with actual conversations

@modern-fireman-99755, I've sent you a DM. thankyou

Hey all, I've added all of my design revisions and improvements here: github.com/OpenHands/OpenHands/pull/16276 Take a look and let me know what you think. 🙂 @hundreds-twilight-32833 @millions-afternoon-47582 @limited-student-10747

Big fan. I really want to see how this looks on the OSS view with all of our various automations running

Awesome, how will it look when we have 16 entries?

It should grow down, then you can pin the ones you want always visible

Sounds good, and can we turn it into a dashboard?

Screenshot 2026-08-03 at 10.14.57 PM.png

Awesome, looks fantastic

I think having a "type" property on the automations would help move us in that direction. It would let you group them for SDLC

@millions-afternoon-47582 could you re-jigger the design to follow the one Paul came up with? Thank you!

Yes, I will review his pull request. Thank you very much! thankyou

Looks great so far @millions-afternoon-47582. It seems to be missing the pin functionality to add the dashboard like cards

Yeah, agreed this looks great! Hopefully we can add the pin functionality

I know its a lot to untangle with a whole new PR! This is what it looks like from Pauls PR (I still had it running local)

The feature hasn't been lost. In my first video, there was only one automation, so this feature wasn't visible at that time. For additional context, please refer to the video below. I hope this helps clarify the behavior. Thank you very much! thankyou

Awesome Hiep, I think maybe the easiest way for us to verify this would be to get it running on the VM, could you update the agent canvas on the vm there?

Yes, I'll deploy the changes to our VM. Thank you very much! thankyou

Looks correct to me

Hello everyone, I've deployed the latest changes to our VM. The feature is now available for testing there. Thank you very much! thankyou

Very nice! I think this is good enough to merge personally, but one small thing is that when we have many automations and a somewhat short window, there is a lot of blank space at the top of the interface, with the automations flowing off the bottom.

I’ll work on resolving this issue. Thank you very much! thankyou

I think we could move the “let’s start building” window up a little bit, and then maybe make the automations a scrollable window that fits within the overall window pane

@millions-afternoon-47582 Please don't just yet. @limited-student-10747 that space is intentional. The new chat page is still the "New Chat" page. Haveing the main action front and center is still desirable. The extra top padding is a conscious design decision. Turning this page into a pure dashboard that subjugates the primary function is not good—we should consider creating a true dashboard page that is separate then.

One other thing is that we don’t have great visibility into when an automation is actively loading the first time. Maybe a loading spinner would be good.

Then I think it's worth slowing down and working on a separate dashboard page

I think this is good incremental progress though, happy to go with this (as long as we fix the design of the bottom part), and we can discuss the bigger changes later

I missed something then, what's the issue with the bottom part?

Go here and log in : oss-agent-canvas.ngrok.dev And you’ll see that the automations flow off the bottom of the screen

That's intentional. Github copilot does the same. It allows us to add more to the bottom of the page if we need to. There's other components such as a recommended automations rail, and some other temporary modules that we might place on the page. At least that was the original intention/

Ah, OK, if that’s intentional design I’m OK with going with it, but I’d not seen any chat app with that format before

copilot for ref

most don't have anything on this page other than the primary composer 🙂 Github copilot is the only that has additional content and I believe they're doing the best that's aligned with our goals here.

Got it, it does seem that github puts the chat app right at the top of the screen though? thinky spin

If I understand correctly, there aren't any changes needed at this time. @limited-student-10747, could you please review the pull request when you have a chance? • feat: ship the featured automations landing dashboard Thank you very much! thankyou

Yes, correct! I approved, and we can make improvements later as we get more ideas.

for example, can we limit the number of automations. I think it is not so cool to scroll on the main page

I think ultimately we'll need to make this configurable for the user. Also have it on our todo to port over some of the new UI elements Paul created to the dashboard Hiep just worked on for Automations 😄

Yeah, I think this is a great start, and we can convert it into something more configurable

There are several features I made sure to test and double check the design accommodates the most information in the tightest design. Scrolling here is a feature, not a bug, to accommodate additional items we can put into the page. As we move forward we can consider how to make the dashboard configurable by the user. Ultimately the dashboard is if the user wants to modify the layout of the page themselves in code. Currently: • The automations list will show 10 with a view more and top out at 20 with a view all that goes to the aumations page. • The pinned items will have a view more at 6, when clicked it will show all pinned • The pinned cards are moveable, you can grab and hold to reposition—so they aren't fixed based on the order that you originaly pinned • The status bars in the cards no longer wrap, errors will appear in a hover tooltip • The sparklines of the past conversations have hover effects and are also clickable. In the pipeline: • A rail of recommended automations • A toggle above the composer to switch between Code and Automate—this nudges people to create more automations, not just new chats • Additional reminder messages to try automations or other features the user has not yet done • Other metrics containers as demoed in Rajiv's automations dashboard (or we decide to move to a full dashboard separate from the New chat page) Last remark, I know Factory is getting referenced a lot right now as a benchmark for dashboards, but the dashboard is NOT their New Chat page. That is not the first screen the user sees, their New Session page is below. They're current UI paradigm follows what we and every app is doing in the space—New chat/session is a clean slate to start a new chat session. Github Copilot is really the only competitor adding more content, and even that is below the fold of the viewport.—That's the best paradigm if we are going in this direction and the one I recommended to Devin before he showed me Copilot.

Hey Paul, sorry, I just saw I never responded to this, but thanks a bunch! Super-informative