This message was deleted.
# openhands-cloud
d
This message was deleted.
s
assigned a brand new ticket - same new error:
l
Sorry, we’re taking a look!
Hey @strong-grass-72776, apologies, we looked at the server logs and it seems like this error happened because you ran out of OpenHands Cloud credits. This error is surfaced in the UI, but not in the github resolver, so we need to fix that. Separately, we’re working on enabling context compression to make resolving each issue less expensive so the credits will stretch longer. I hope we can get both of those fixes in soon, maybe as early as Monday or Tuesday next week.
@quick-window-91705 could you take a look at this one? https://github.com/All-Hands-AI/openhands-cloud/issues/16
👀 1
s
ahh I see ... then I would also strongly request you add an auto-refill capability ...
nod 1
l
That’s a good idea, opened an issue here: https://github.com/All-Hands-AI/openhands-cloud/issues/17 (if you comment or give a thumbs up that’ll help us prioritize!)
s
@limited-student-10747 is team billing part of the committed roadmap or do you need a ticket for that? I made my team a shared brex card for openhands but if everyone has separate balances to top off their own accounts too, this is unmanageable
l
Ah, yes, it was already on the roadmap but we didn’t have a ticket open, just opened it here: https://github.com/All-Hands-AI/openhands-cloud/issues/18
(thanks for all the feedback!)
s
for sure 👍
oh one more - are you planning to show the cost for each session? and also the cost for each request within the session? Devin supports both of those ... the session cost is most important, but the request cost is key to identify where context has gotten too large
l
Cost for each session is available by clicking the bottom right. We don’t have request-by-request cost. (But in terms of the context getting too large, once we turn on context compression it should be much better.)
s
ohhh - I didn't see it, and my team was asking, so I don't think anyone saw it
also, i'm sure context compression will help, but Devin has gotten a lot more efficient over the last month or two, and it could be they are just reducing their token -> ACU conversion, but reading the between the lines, I suspect they are managing the context like a stack trace in their planner - so each time Devin moves on to the next planned task, it just has the purpose of the overall session and the current task it is doing
👍 1
l
Thanks, that’s good info!