What's our plans for Plugins and Skills (found und...
# proj-agent-canvas
e
What's our plans for Plugins and Skills (found under the
Customize
menu)? Will we be letting users configure the Plugin and Skill repos OpenHands should pull from? Will we also be supporting
/plugin
slash commands?
h
Skills pull from .agent folder locally. I think plugins now does the same but I've not tested it yet. What do you mean with:
letting users configure the Plugin and Skill repos OpenHands should pull from
Also not sure about the
/plugin
slash commands? Do you mean commands that a plugin might bundle as part of included skills?
e
As an individual user running Agent Canvas on a local backend, I can: • Manually skills to my local ~/.openhands folder so they can be used in an Agent Canvas conversation [done] ◦ GAP: Which folder is this? Do we document it? • Have a way interactively in Agent Canvas (either via Customize > Skills or via a slash command) to save a skill to my local ~/.openhands folder ◦ Currently, the
/add-skill
command saves this in teh workspace only, and doesn't make it available to future conversations i have locally in Agent Canvas • Install pluigins to my local ~/.openhands folder. I should be able to do this via a command like this:
/plugin install superpowers@claude-plugins-official
• Add a Plugin Marketplace to my Agent Canvas so I can browse available plugins. From there, I can then selectively install specific plugins. I should be able to do this via Customize > Plugins screen ◦ GAP: Customize > Plugins screen is empty
m
Add a Plugin Marketplace to my Agent Canvas so I can browse available plugins. From there, I can then selectively install specific plugins. I should be able to do this via Customize > Plugins screen
Hello everyone! We've completed this work, and it will be included in the next Agent Canvas release thankyou
> Install pluigins to my local ~/.openhands folder. I should be able to do this via a command like this:
/plugin install superpowers@claude-plugins-official
We now have a UI for adding plugins, and installed plugins are automatically loaded into conversations. These features will be included in the next Agent Canvas release. We don't currently support a command like that thankyou
e
Cool - the UI is probably fine for now!
Hiep, when's a good opportunity for Devin and I to get a demo?
m
You can refer to the video below for more information. To try the feature, simply pull the latest code from the
main
branch and run
npm run dev
. If it would be helpful, I'd be happy to join a Zoom call to walk through the feature and provide a live demo. Thank you very much! thankyou
h
You can add a plugin if you are using main right now. The UI is in place. Since Hiep did the work there I bet we could port it over to skills as well. Not sure about the marketplace functionality
🙌 1
e
Cool. A few pieces of feedback: • We should probably provide some examples of source, ref and path values (using a real-world example) so folks can understand how to fill this form • A common pattern for installing a plugin is doing a command like this:
/plugin install superpowers@claude-plugins-official
◦ We should prioritize that as a followon enhancement • After Installing a Plugin, we should make it possible for a user to browse the contents of that plugin. Example from Claude Code Web UI
h
Agreed. This was a quick first pass to include plugins so we don't have the placeholder page. Paul did some design work for the previous GUI that should help guide showing the contents of plugins
e
For sure! 👌 to see the progress here, just wanted to capture some follow items 🙂 Is there a good place to make tickets for this or are they already captured
h
I can create some issues in AC. Maybe group them into a Skills+Plugins milestone. I don't know if there are any MCP ideas floating around but maybe a Customize milestone if there are.
e
That would make sense - something that rounds out the use cases / friction around Customize use cases
nod 1
Also, what's the behavior for 'Installing' a Plugin in a Cloud backend? I'm guessing the Plugin is downloaded dynamically at the start of the conversation, rather than actually being stored on the cloud.
m
We automatically load the list of plugins from local folders and the OpenHands extensions repository. As a result, the Install button may be redundant. We may consider removing it and keeping only the Enable/Disable functionality to simplify the experience thankyou
e
But let's say I discover this plugin that I want to use:
/plugin install superpowers@claude-plugins-official
And I would like to use that Plugin within an OpenHands Cloud conversation Would I be able to 'save' that plugin to my OH Cloud account, and then have it dynamically downloaded at the start of my OH Cloud conversation?
c
I can create some issues in AC.
Sorry I’m dense, what does AC stand for, here?
m
Based on my understanding, this is not currently supported on OpenHands Cloud. At the moment, it is supported only by the Agent Canvas local backend. Currently, dynamically downloading plugins at the start of a conversation works with the Agent Canvas local backend. Once we support a command such as:
/plugin install superpowers@claude-plugins-official
the installed plugin would be saved automatically, displayed on the Plugins page, and automatically loaded into new conversations thankyou
what does AC stand for, here?
I believe it stands for Agent Canvas thankyou
nod 1
😅 1
thanks on a stick 1
c
😅 Thanks! I call it canvas 🤷‍♂️