Turn openhands App into a PWA (Progressive Web App)

[happyherp]

What problem or use case are you trying to solve?

When I develop with openhands, it is effectively my IDE. So I often use that particular chrome-tab. But from windows perspective it is just one chrome tab, in one chrome window. So sometimes when I want to switch back to it, i have to spent some time to find it. Especially if I by mistake opened another tab in the window with openhands that now has focus.

This can be improved a lot by turning it into a PWA Progressive Web App.
Then you get this:

You can try it right now.
ChatGPT:

Step-by-step fix: make Chrome treat your app like a standalone app
Find the shortcut Chrome created (on your Desktop or in the Start Menu).

Right-click → Properties.

In the Target field, you'll see something like:

"C:\Program Files\Google\Chrome\Application\chrome_proxy.exe" --profile-directory="Default" --ignore-profile-directory-if-not-exists http://127.0.0.1:12000/
Change it to launch Chrome directly with app mode, like this:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --app=http://127.0.0.1:12000/
(Note: chrome.exe, not chrome_proxy.exe.)

Click Apply, then OK.

I did that, works pretty good.

• own spot in taskbar with own icon
• own spot in the Alt+Tab window
• more space because the browser bars are gone

Describe the UX of the solution you'd like

Would be nice to give everyone that experience with one click.

Do you have thoughts on the technical implementation?

Apparently that is possible by editing like 3 files. I think @openhands-agent will one shot this.

Then we would get this in the address bar:

Describe alternatives you've considered

Additional context

[happyherp]

@openhands-agent give it a shot!

[happyherp]

lets try again @openhands-agent

[happyherp]

lets try again @openhands-agent

[enyst]

@happyherp Sorry I didn't clarify well on slack. This is confusing, please let me clarify, there are 2 agents:

1. openhands-agent is the open source resolver documented here: https://github.com/All-Hands-AI/OpenHands/tree/main/openhands/resolver#using-the-github-actions-workflow

Generally, it will not work from a fork (because it uses this repo's credentials and GitHub enforces it), and, also, the account needs merge permissions on this repo: https://github.com/All-Hands-AI/OpenHands/actions/runs/14280087683/workflow#L69

You can set up open hands-agent on your own repos (including a fork of this repo), there it will work for you and collaborators on that repo.

2. OpenHands is the cloud resolver. You can tag the cloud resolver with @ OpenHands (without agent), for that it uses your cloud account and it should work afaik. I think? 😅

(this issue is a very nice UX idea! 😃)

[happyherp]

@enyst Thanks for the follow up. When I posted the last the comments, I had already copied the issue to my repo happyherp#16 But because I kept posting in the wrong issue (this one), nothing ever got triggered. Now I know why.

[happyherp]

But I got to try the @OpenHands