feat: plugin system over the existing seams (#64) - #77
Merged
Conversation
A plugin = directory with jsclaw.plugin.json ({id, version, entry})
whose entry exports activate(api); api registers into the four seams
that already exist: registerChannel (channel registry),
registerCommand (slash commands, host-side), registerGatewayMethod
(WS dispatch), registerMcpTool (gateway /mcp). Config speaks
openclaw's shape — plugins.{enabled, allow, deny, load.paths,
entries.<id>.{enabled, config}} with deny > allow > entry semantics.
Failing plugins warn and skip, never crash the gateway. Plugins
extend the gateway; agent capabilities remain MCP's job. Example
plugin in examples/plugins/ping as the contract's living docs.
This was referenced Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Built to the audited PoC scope on #64: jsclaw.plugin.json + activate(api) over the four seams this week built (channel registry #51, command registry #60, gateway dispatch, MCP tool table #73) — nothing invented. openclaw's exact config shape and policy order (deny > allow > entry.enabled, default-on, per-plugin config delivered to activate). Boot-time dynamic import with warn-and-skip degradation. examples/plugins/ping demonstrates all three host surfaces (slash command, WS method, MCP tool). Deferred per audit: install sources (clawhub/npm/git — load.paths only), slots, typed hooks, provider zoo, compatible bundles. Runner-side tools intentionally never (MCP's job). Tests 156/156.