Here is a video of experimental Agent Canvas exten...
# proj-agent-canvas
c
Here is a video of experimental Agent Canvas extension system I showed at demo with a genuinely useful plugin -- or at least it's useful to me. What I am attempting to show here is that it would be entirely possible to build a future state OpenHands Enterprise UI as Agent Canvas extensions that live in their own repo. github.com/OpenHands/agent-canvas/pull/1659 github.com/jpshackelford/agent-canvas-experimental-extensions
🎉 2
❤️ 1
PR is still very rough with extensions api in serious flux and incomplete... but at least this starts to paint a picture.
If you ever wanted to reuse a cloud sandbox across multiple conversations -- even if the sandbox was paused -- this might be useful to you as well.
e
This is so cool
c
conversation panel extension point
❤️ 1
e
@hundreds-twilight-32833 does this overlap with your vision for extensions? How can we bring the best to both worlds together and ship this even if it’s experimental or labeled beta?
This is pretty differentiated and helps us reinforce our open source and customization defensible differentiator
h
I think in broad strokes it does. I have not dug too deep to see how build steps are handled or if you can have an extension built+run+installed from inside canvas but that is something I’d want to run through. Hermes is working on a plugin interface expansion to support more hooks and integration layers within hermes github.com/NousResearch/hermes-agent/issues/64182 which could be a good thing to look at if we want to really tackle this (which I’d love to do 😄 )
c
With the system today you can build and iterate on extensions in the same agent-canvas instance by specifying the extensions to load as an environment variable. It would be nice if the ui also just let you point to a local directory w/ a git repo. Build step is not mandatory unless you want to distribute as an npm.
e
How ironic that Hermes issue was created hours after John-Mason's slack message 🙃 Devin, what hesitation do you have around this general feature idea? It seems powerful and something that might apply to both OSS users and Enterprise customers (who eventually adopt Canvas and want to customize their experience)
h
Nothing major on my end right now. It is a big pr and it’ll need some eyes
c
Yes, to pursue this we'd break into a set of PRs that could be phased in and reviewed incrementally. There is a linked architecture doc that talks about how it works and probably we'd want an architecture discussion that vets the overall approach before we do that.