On the new Cloud, the redesign looks neat! When t...
# openhands-cloud
c
On the new Cloud, the redesign looks neat! When the server is stopped (new -ish status message "server stopped"), it eats user messages: what I wrote "disappears" into the nether, it's lost, on refresh it seems you need to retype it. Maybe the new status is somewhat less obvious I think (smaller text, position), so... atm it keeps happening šŸ˜…
w
yeah I agree it's harder to spot the new status text
disappearing text is definitely not intended though
CC @millions-afternoon-47582
šŸ‘€ 1
m
I've created this Github issue (https://github.com/All-Hands-AI/OpenHands/issues/11056). Thank you! thankyou
w
m
If I understand correctly, what Engel mentioned aligns with the feedback you shared previously. Is that right?
Ideally I could also send the message and see it appear, and then it goes to the agent once everything is ready
w
šŸ¤” I think these are two different issues: • Bug: "disappearing messages": if I type in the box, but don't hit enter, sometimes the text disappears (e.g. if I shrink the window enough to switch to mobile mode) ā—¦ I think this is what's happening to Engel, but unsure • Feature request: let me hit enter before the server is ready to populate the first message ā—¦ right now we disable submit until the server is ready
m
Yes, I will confirm this with Engel Hi @calm-artist-7206, I would like to confirm my understanding of the behavior you described: • When the status is ā€œServer Stoppedā€, it is still possible to type a message without any issues. • However, upon pressing Enter, the message is not sent and the text input is cleared. • After refreshing the page, these unsent messages do not appear in the chat interface. Could you please confirm if this is accurate? We can refer to the video below for more information. Thank you! thankyou
w
ahhh yes that does look like a different bug!
thankyou 1
c
As your video shows @millions-afternoon-47582, I did send the message, I pressed Enter, and it went poof. I looked at the status, it was ā€œstoppedā€.
thankyou 1
Just a thought here:
• Feature request: let me hit enter before the server is ready to populate the first message
ā—¦ right now we disable submit until the server is ready
+1 on that feature request (I'd call it usability bug fix), because of this: because maybe what applies to first message, should apply to first message when a session needs restored, and it doesn't Currently, the disabling behavior seems to tell the user "we prevent you from submitting when the server isn't ready, sometimes... other times you just go ahead, write half a novel and send it over, to... whoops, it went poof"
thankyou 1
nod 1
m
Yeah, that makes sense. Thank you! thankyou