They are setting up one Canvas per "use case" so t...
# proj-agent-canvas
w
They are setting up one Canvas per "use case" so that each Canvas gets exactly the credentials it needs
h
I wonder if a config file on start or something could help make this use case easier. I think someone also had the idea of a global git repo for a specific backend/instance so all your automations and extensions could get synced to a specific repo.
w
yeah I like that
for now just supporting "global skills" with /add-skill would be great
I think we call them "auto-discover skills" right now
h
Its really just the same as us preloading the extensions skills
w
syncing a repo is a whole thing though. honestly I just want to type some markdown
h
A markdown editor there should be pretty straightforward. I do like the other idea as well. Not sure how it stands up against something like plugin marketplace docs.openhands.dev/enterprise/plugin-marketplace
nod 1