would love others thoughts on this <github.com/Ope...
# proj-agent-canvas
e
would love others thoughts on this github.com/OpenHands/OpenHands/pull/18995
h
Neat idea! When running sandboxes that need to be started to interact I could definitely see the appeal. I'm not sure about such a prominent button. I could see that eating a lot of resources if everyone was using it every time they logged in to a shared instance (cloud, personal, or enterprise). A completely different way to approach this could be a dashboard/inbox view where you can see the status and output of all your recent conversations. So you could then wake up anything that needed human review or intervention easily. I've seen some ideas for something like this...maybe a kanban view, an orchestrator like UI/UX.
e
i think the best approach would be to do something like cursor where startup times are optimized and pending messages are abstracted away to the point where you don’t actually feel that anything ever goes to sleep. but this was the short term fix in my mind
like i don’t need to know that the message is pending if openhands recevied it and its in a queue to send and i know it’ll be sent, just show it as sent
and don’t make the agent wake up to show me the recent messages, just store it and show it and start waking up in the background.
but my wake up button was a short term bandaid to hide my pain lol
h
startup times are optimized and pending messages are abstracted away
Cloud has some runtime speed improvements that have come in recently but I think its always a target to improve. I don't have as much coverage on the enterprise side but I think there are some specific things that can be done when a company deploys their own OpenHands instance to tweak the sandbox startup times and customize for needs
app.all-hands.dev (cloud) has more general sandbox configs
e
I think we can abstract away the idling / startup from the user though which would be a big UX improvement
thinky spin 1