Updated Mockups for the Backend Selector with changes to copy, removing the prominent Enterprise columns, and getting more exact with the options: OpenHands Cloud, Local agent-server, Remote agent-server. We can point the full-width comparison link to an updated docs page for users looking for Enterprise options: github.com/OpenHands/OpenHands/issues/15426#… cc: @calm-artist-7206 @limited-student-10747

Thanks @hundreds-twilight-32833! Just to clarify, why do we need the distinction between “local agent server” and “remote agent server”?

One is on my computer, one is not

But aren’t the settings the same? “host name”, “host”, and “api key”

basically, one needs auth, the other doesn't?

Yes, same settings as far as I know. API could be required for remote and the documentation as well as mental model is very different

I think the mental model between the automatically populated agent server and the separately run agent server is very different. But I’m less sure about the mental model difference between locally/remotely run agent servers

I think it helps a lot with in-app education to call them out and highlight they exist

The security concerns with running the agent are different and feel different

Yeah I guess I agree with this but the agent server ones are almost completely the same and the cloud is very different, which makes me feel like putting them in parallel on the sidebar would be a little confusing

It's a reasonable possibility, though do you feel strongly about it? Because while that makes sense, I think maybe the cloud shouldn't be that different… It doesn't feel different from user perspective, does it? I would think of it as an agent-server in a hosted cloud, so I’d expect some auth and then… an agent-server (or a similar API with the agent-server, proxied by the cloud app-server 🤔)

I dunno, cloud does feel pretty different. Here’s the workflow: local agent server • run agent-canvas --backend-only, record the session API key • run agent-canvas --frontend-only, enter the host, session API key • use with non-ephemeral sandboxes, canvas-only-config, etc. remote agent server • ssh into another machine ◦ run agent-canvas --backend-only, record the session API key • run agent-canvas --frontend-only, enter the host, session API key • use with non-ephemeral sandboxes, canvas-only-config, etc. cloud • run agent-canvas --frontend-only • log in to the cloud and have the backend automatically populated • use with ephemeral sandboxes, canvas+cloud config, etc.

I've been playing with this a little, I think maybe we can do like two ‘types’: • agent-server • cloud and see what people think?

I agree of course 🙂

Think your agent could generate a wireframe to add to the issue? I've got this on my todo to circle back to this week either way 🙂

@bland-bear-604 can you help us here?

🐾 Pounced on it — wireframed the two-path idea (Agent-server / Cloud), with Local vs Remote as a sub-choice inside Agent-server since the only real difference is Remote needing a session key. Enterprise stays out of the modal; just a subtle “more about deployment options” link. Dropped it on the issue with the image: https://github.com/OpenHands/OpenHands/issues/15426#issuecomment-5119749035 Low-fi on purpose — poke holes in the structure, not the pixels. 😁

That doesn’t seem great 😅 The LLM overfit on what we were discussing most of the time

image.png

I do like it

This looks great @hundreds-twilight-32833, thanks! Could you share the screenshots of the other options (agent-server remote and cloud) for completeness? Then I’d be ready to rubber stamp

Could we keep agent-server first, cloud second?

I agree that agent-server can be first and cloud second

Thanks for all the feedback! I hope the additional docs help folks 😄

Do we have a PR for this? If you need any help landing it Hiep can probably help

I have a branch I showed to @breezy-kilobyte-39430 and he wanted to look at it as well for some UI cleanup before making a PR

OK sgtm