Skip to content

feat: support Claude SDK plugins option on workflow nodes #1118

@norbinsh

Description

@norbinsh

Context

I'm building a custom workflow that relies on Claude Code plugins and noticed that while Archon supports skills, mcp, and hooks on DAG nodes, there doesn't seem to be a way to pass the SDK's plugins option through to query().

Checked:

  • Searched existing issues/PRs — nothing related
  • Confirmed AssistantRequestOptions and the dag-node schema don't expose a plugins field
  • The feature-coverage matrix lists "Plugin system" as not covered

The Claude Agent SDK supports plugins: [{ type: 'local', path: '...' }] on query(), which loads full plugin packages (skills, agents, hooks, MCP servers from a .claude-plugin/ manifest). This is distinct from the existing skills: field which loads individual skill directories.

Proposal

Add an optional plugins field on command/prompt DAG nodes (Claude only, same scope as skills):

- id: review
  prompt: "Review this code"
  plugins:
    - ~/.claude/plugins/my-plugin

The implementation would follow the existing pattern for skills/mcp/hooks — schema field, executor wiring, client passthrough. Fairly small surface area.

Status

Experimenting on my fork. Happy to contribute a PR if this aligns with the project direction. Totally possible there's a reason this was left out (complexity, plugin API stability, etc.) or that i miss something here - would love to hear thoughts before going too far.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Low priority - Nice to have, consider closing if stalearea: workflowsWorkflow engineeffort/lowSingle file or function, one responsibility, isolated changefeature-requestNew functionality (external suggestion, needs review)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions