Is there any specific reason the CLI doesn't support organization skills? How would we fill about implementing org skills the same way as GUI? (Cloning into a temp dir on conversation init and loading into memory) Possibly with a flag to allow, not allow, always allow specific orgs

It may have been lost in the V1 rebuild, and I think maybe I've seen we had some hesitation how needed they were

I can lift what the GUI does which is pull to a temp folder -> load into memory -> delete temp folder But I also don’t want to slow down the CLI speed

Yes, for other reasons than org, even, I feel some kind of references list... makes a lot of sense - there's a bit of a void we need to fill

Yea makes sense - I'll mess around with it Right now the biggest items I'm trying to figure out is User Org Project Levels of skills and MCPs

Sorry to jump to this too, are you familiar with the "plugins" a la Claude Code?

Only by name - I just moved to Claude this weekend (over codex)

I think what people are working on, is to make plugins and marketplaces work - specification is compatible with Claude Code definitions, and we have some extensions. As far as I know, the fundamentals are implemented, so this could also work maybe like: • write a simple json to define a "marketplace" - it has references to plugins • package the Skills you want in a plugin (or more, whatever makes sense to you) - again it's a simple json to say where it is, I think • then reference the marketplace/plugin -> a one-liner should be enough

openhands --plugin m/plugin

or something Or maybe even ignore the marketplace, and

openhands --plugin plugin_ref

This makes sense - so effectively create a marketplace for your organization (which can be private) and then put all our skills in their Kinda like a homebrew tap

Oh yes, does this work? https://github.com/OpenHands/OpenHands-CLI/pull/502

Looks like we need https://github.com/OpenHands/software-agent-sdk/pull/2031 first

Just a side thought I'd like to add: in my view, as of now, Agentskills are much more useful, much more widespread, than plugins. And they're not alike: • Agentskills (and MCPs) are an open standard, and seem "everywhere" • while plugins is an Anthropic attempt, which may or may get changed, "shipped" or "unshipped", may or may not get enough buy-in in general from people In other words, I feel it might still be useful anyway to support org Agentskills or random Agentskills references, not "require" to go through plugins. They're not mutually exclusive IMHO... That said, a "plugin" is the most lightweight packaging ever: just a directory, with sub-directory "skills" / other sub-dirs 😅

Yea, looks really simple Will still need to figure out how to support dynamic scope mcps as well https://code.claude.com/docs/en/mcp#project-scope

c.f. https://github.com/OpenHands/OpenHands-CLI/issues/407