Fix issue #5817: [Bug]: When websocket disconnects, status bar says "Agent is Stopped", even if the agent is still running #5819
+86
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request fixes #5817.
The issue has been successfully resolved. The AI implemented a complete solution that directly addresses the core problem where the frontend incorrectly showed "agent has stopped" when the websocket disconnected.
Key changes made:
DISCONNECTED
state to handle websocket disconnectionsThe solution is comprehensive as it:
This can be confidently sent to review as it addresses all aspects of the original issue while maintaining good software engineering practices (testing, i18n, proper state management).
Automatic fix generated by OpenHands 🙌
To run this PR locally, use the following command: