Let's say I'm a developer and looking to standup the OpenHands front end, use it to run multiple convos, and maybe create a few automations. Which repo should I be using?

I think the user will be given a single docker command or npm command, they wouldn't clone any specific repo

OK, what if I want to contribute? Does it depend on which feature?

Yepp

I think that is what I'm most excited about...getting in there and working on the frontend to make some PRs on the UI

Definitely. I think we also just need to make it easy for someone who’s new to the project to understand how to download the thing that we want them to download, and how to navigate the multiple repos to make contributions

We also are planning on refactoring the repos, but here’s my initial idea: • OpenHands/OpenHands (MIT, TypeScript): will contain the current contents of OpenHands/agent-server-gui • OpenHands/software-agent-sdk (MIT PDF): will be used as the backend for OpenHands/agent-server-gui • OpenHands/enterprise-app-server (proprietary, Python): app server from current OpenHands/OpenHands, imports OpenHands/software-agent-sdk • OpenHands/enterprise-gui (proprietary, TypeScript): the saas gui, uses modules from from OpenHands/agent-server-gui • OpenHands/automations: not 100% sure where this fits in This would make the division between OSS code and All Hands proprietary code clear, cleaning up a lot of the issues we have with OpenHands/OpenHands now.

Thinking about repos structure: • OpenHands/OpenHands (MIT, Python): the current contents of agent-sdk + automations + installer script ◦ commits history: merged • OpenHands/agent-canvas (MIT, TS): an easy to use Admin UI for the agent-server interface to the agent(s); installed by installer script ◦ commits history: new • OpenHands/enterprise-app-server (proprietary, Python): app server from current OH/OH, dependency on OH/OH to run agents in the Cloud/on-premise ◦ commits history: not sure; probably from current OH/OH? That was Ray’s preference when we last talked about it. I think some cut-off is an alternative. • OpenHands/enterprise-gui (proprietary, TS): the SaaS gui, not sure if it uses or the agent on schedule keeps it updated from agent-canvas • OpenHands/automations - moved to OH/OH, for event stuff (entry from GitHub, entry from Slack), not sure about the scheduled stuff