Skip to content

feat(plugin-tooling): compile a plugin into an Agent Plugins directory - #375

Closed
fnzko wants to merge 11 commits into
symposium-dev:mainfrom
fnzko:plugin-compile
Closed

fnzko wants to merge 11 commits into
symposium-dev:mainfrom
fnzko:plugin-compile

Conversation

@fnzko

@fnzko fnzko commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Part of #277.
Depends on #332 (until it merges, only the last commit is new here).

An author who wants to hand their plugin to an agent directly, without Symposium, has no way to get the directory agents load. Symposium builds that directory only for plugins a user enables with use --global.

Now cargo agents plugin compile <dir> --out <out> validates a plugin or skill directory and writes <out>/<name>/ with plugin.json, the same manifest in .claude-plugin/plugin.json, and the skills. It then prints how to load the result in each agent, for example claude --plugin-dir. Running it again replaces its own output. A directory it did not write is left alone, and nothing else under <out> is touched.

Verified with integration tests, and in Claude Code and Copilot CLI with --plugin-dir: each agent loads the plugin and its skill, and claude plugin validate passes.

Take into account:

Disclosure questions

AI disclosure.

  • The AI tool authored large parts of the code

@fnzko

fnzko commented Oct 20, 2026

Copy link
Copy Markdown
Contributor Author

Closing for now: it builds on #332, which waits on the plugin delivery decision.

@fnzko fnzko closed this Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant