You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just trying out OpenHands now, using the docker container setup. I tried to create a tetris game in HTML. However, from the best I can tell, the OpenHands GUI's browser maybe isn't showing enough FPS to view the Tetris game? Unless I'm wrong and it's just not working.
So, the next thing I try is to open the workspace in VS Code. I figure I'd use a live server or Simple Browser command or something. However, neither of these seem to be an option. Simple Browser doesn't show anything at all, and every "live Server" extension I could find to install in VS Code tried to open a port that was only accessible within the docker container.
So that said, either: 1. Increase the FPS of the GUI's browser and/or 2. Provide a way to use the exact same browser within the VS Code tunnel provided by the VS Code button in the GUI.
The text was updated successfully, but these errors were encountered:
Hi there is a feature that will be released soon which will let you access the app OpenHands runs in the container.
I'll circle back once it's released to see if that satisfies your scenario.
I'm just trying out OpenHands now, using the docker container setup. I tried to create a tetris game in HTML. However, from the best I can tell, the OpenHands GUI's browser maybe isn't showing enough FPS to view the Tetris game? Unless I'm wrong and it's just not working.
So, the next thing I try is to open the workspace in VS Code. I figure I'd use a live server or Simple Browser command or something. However, neither of these seem to be an option. Simple Browser doesn't show anything at all, and every "live Server" extension I could find to install in VS Code tried to open a port that was only accessible within the docker container.
So that said, either: 1. Increase the FPS of the GUI's browser and/or 2. Provide a way to use the exact same browser within the VS Code tunnel provided by the VS Code button in the GUI.
The text was updated successfully, but these errors were encountered: