I think it’s not very clear how to install an extension from the dialog here. It’d be nice to have some instructions.

@hundreds-twilight-32833 any chance we can link to the Docs directly from the Customer>Extensions page? docs.openhands.dev/openhands/usage/agent-canvas/canvas-extensions Also, it would be great to start building a public ecosytem of extensions. I think this is going to be critical for early traction, especially for users who want to install a few and see how it goes. I imagine most users will want to install existing extensions first, before building their own. One thing I noticed is the

Source

field is finnicky. For example,

GitHub:owner/repo

fails, while

github:owner/repo

succeeds. Ive also been unable to just 'drop in a Github URL and go' -- it's not clear what GitHub URL I should use

Yea I think we could directly link there. That would help. I also found the fields to be not quite right github.com/OpenHands/OpenHands/issues/17048. Can you add what you tried to that ticket so we can try to address it all together

The main issue I had was that I opened the modal and then it didn’t have any directions on how to proceed. I think we could link to the docs and then also the OpenHands/extensions repo

start building a public ecosytem of extensions.

I'd like to settle on a good long term name first before we add that to the extensions repo (or elsewhere). Canvas Extensions could work but it isn't as easy to describe. Working on that bit separately

Also, we need to figure out the naming before we launch, since “extensions” is already used as the umbrella term for all things, including skills, mcps, etc.

• Add-ons, Packages, Apps?

◦ Install OpenHands Add-ons to extend the Agent Canvas platform without forking so you can introduce custom functionality inside canvas.

◦ Install OpenHands Packages to extend the Agent Canvas platform without forking so you can introduce custom functionality inside canvas

◦ Install OpenHands Apps to extend the Agent Canvas platform without forking so you can introduce custom functionality inside canvas

I've been trying to write about them to see what reads/sounds good

I like “App” if it’s something that installs lots of things. If it’s just an extra sidebar, maybe “Page”?

OK yeah, once we figure out a name, we should still think of an ecosystem strategy here. I have a strong opinion that most users will want to install an existing extensions/add-on/app before creating their own, and there's opportunities to have the ecosystem solve use cases we can't/won't solve directly within Canvas

Yep, sounds good. I think the solution to my complaint above is to add examples to the OpenHands/extensions repo. Personally I think “app” is a good name. Everything about this feels like an app to me (it’s somewhat self-contained on its own page, and it has a fixed set of functionality). But if for whatever reason we don’t like “app”, then “package” would also be OK with me.

😄 Let me run through it for like 10 mins. Testing some different GTM packaging

OK, sounds good. Nothing like a little decisiveness to move things forward 🙂

Joe was just nudging me in a DM as well. Appreciate it

perfect, let’s do it! as a next step we can start uploading example apps to the OpenHands/extensions directory, and add a link to the UI so that people can explore existing apps. In the somewhat longer term, we could design an app browser like we have for automations

🎉

@fresh-machine-37269 open an issue on the OpenHands/extensions repo for the former, and OpenHands/OpenHands for the latter, with the latter being blocked by the former.

🤖 On it! View progress here: oss-agent-canvas.ngrok.dev/conversations/…

github.com/OpenHands/OpenHands/issues/17058 and PR in progress