What is the status of "Tasks" on the Cloud? I thin...
# openhands-cloud
c
What is the status of "Tasks" on the Cloud? I think there was an idea that it would be possible for users to set some tasks to be run periodically? And monitored from the UI in some manner. Or have I taken up hallucinations instead of GPT-5? 😅
e
Interesting... like some sort of cron task?
c
Yes!
l
@elegant-branch-54423 I think you were thinking about a kanban-style task board at some point?
c
Maybe I was dreaming about the periodic aspect of it?
l
It’s definitely something that we’ve thought about
And it’s something that I’d like too
c
Just for context, I think I need to set up several prompts to be run periodically for the repository. There are multiple options on how to do it, and I don't claim I know which I'd like, even, just thinking to start some asap. For example, they could be GitHub actions, that would be easy and transparent, though we have so many it's easy to forget to check them. Alternatively, they could be set on the Cloud, and then maybe the dashboard feature can show them separately so I can figure out easily / modify easily. Of course, no problem if I just run as normal conversations now. But we did forget some, and they should be repeatedly run, so... the cron aspect / inbuilt reminder could be nice. For example, the REST API is likely not up to date right now. The developer doc on OpenHands architecture is another.
👀 1
e
Re: Kanban-style task board, yeah we've been doing some sketching of a single dashboard that helps you track conversations by PR/repo. Might have some very very rough sketches to share next week for community feedback. For lack of better term, we're tracking this as a "Task Dashboard" on the public roadmap (also got a nice 👎 on the idea in one of the comments lolsob) But I think Engel may be talking about something else 🙂
Engel, that's interesting and makes sense. I'm guessing these prompts could easily be stored as microagents, but then setup on a cron schedule to run? This could be a nice cloud feature given access to on-demand runtimes.
w
A great way to get an MVP for cron agents would be to have a cron GitHub action that uses the SaaS API!
I've been meaning to do this for forever
only issue is it'd use _someone_'s OpenHands account--maybe we'd want to set up a bot user
c
Joe, a most interesting detail in what you said that actually got me thinking is this "on-demand runtimes". What Robert says makes sense. The remote runtimes are nice to run them, but that... doesn't necessarily imply web UI.
s
I think I said something along those lines in a ticket actually... Let me see if I can find it.
c
maybe we'd want to set up a bot user
👍
e
yeah definitely, I agree this sounds like an API-centric use case. Didn't mean to imply a Web UI. Just wanted to call out that the "Task Dashboard" GitHub project is a materially different use case than what we're talking about here 🙂
l
@wooden-umbrella-84098 I just created an openhands cloud user for openhands-agent (for end-to-end testing in CI) and can get someone the openhands cloud API key if you’d like
s
Oh I was thinking of OpenHands-Cloud#59 / OpenHands-Cloud#65 / and #9418 which were closed in favor of #9414. I've linked them to the 9414 issue now.
👍 1
e
I want to say that this ticket (OpenHands-Cloud#59) should largely be fixed with some of the recent Resolver fixes we put in.... I think there's a few things to unpack here maybe: 1. Cron tasks: Ability to setup conversations to run on a periodic schedule ◦ MVP: Use GitHub Actions with a bot user 2. Ability to monitor multiple tasks: I think "Task Dashboard" will somewhat help with this, but it won't have visibility into "scheduled tasks" if you're using GitHub or other system to schedule convos using the Cloud API So I'm guessing a more polished solution would be to have OpenHands Cloud manage the cron schedules so you can have visibility into conversations/tasks that will be scheduled?