docs: clarify plugin style preference · openclaw/openclaw@0340321
steipete
·
2026-04-25
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -54,6 +54,15 @@ We prioritize secure defaults, but also expose clear knobs for trusted high-powe
|
54 | 54 | OpenClaw has an extensive plugin API. |
55 | 55 | Core stays lean; optional capability should usually ship as plugins. |
56 | 56 | |
| 57 | +There are two broad plugin styles: |
| 58 | + |
| 59 | +- Code plugins run OpenClaw plugin code and are appropriate for deeper runtime extension. |
| 60 | +- Bundle-style plugins package stable external surfaces such as skills, MCP servers, and related configuration. |
| 61 | + |
| 62 | +Prefer bundle-style plugins when they can express the capability. |
| 63 | +They have a smaller, more stable interface and better security boundaries. |
| 64 | +Use code plugins when the capability needs runtime hooks, providers, channels, tools, or other in-process extension points. |
| 65 | + |
57 | 66 | Preferred plugin path is npm package distribution plus local extension loading for development. |
58 | 67 | If you build a plugin, host and maintain it in your own repository. |
59 | 68 | The bar for adding optional plugins to core is intentionally high. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
