Scope: Fully Support Plugins in Customize, Conversations, and Automations

[DevinVinson]

Agent Canvas already has the beginning of a Plugins surface, but it is mostly placeholder UI today.

Current state:

• /plugins route exists via src/routes.ts
• src/routes/skills-plugins.tsx renders only a title/description
• ExtensionsNavigation includes a Plugins nav item, but marks it comingSoon
• conversation creation already accepts explicit launch-time plugins through PluginSpec
• buildStartConversationRequest() forwards plugins onto the agent-server conversation payload
• skills are already implemented through SkillsClient.getSkills() in src/api/skills-service.ts
• A plugin can be used in a conversation via the /launch route

Before Canvas implements local plugin discovery itself, agent-server / SDK should expose plugin discovery as the source of truth, similar to skills. Otherwise Canvas could display plugins that the runtime does not actually load.

Dependency

Blocked on SDK / agent-server support for plugin discovery.

Needed upstream:

• agent-server plugin discovery endpoint
• typed PluginsClient in @openhands/typescript-client
• canonical plugin metadata response shape
• canonical conversation plugin source shape, including whether parameters are supported

Goal

Add first-class Customize → Plugins support in Agent Canvas, in parity with Customize → Skills, using the SDK plugin API once available.

[DevinVinson]

This initial focus on this issue is to scope this out and see how many repos this needs to touch and get a breakdown of the work needed. That way we don't have a wide reaching set of PRs trying to tackle this all at once without a clear plan.