Ayuriel/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: clarify plugin compatibility signals

Browse Source
This commit is contained in:
Vincent Koc 2026-03-17 23:27:18 -07:00
parent ad185dd4a8
commit c36a493e80
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/tools/plugin.md
View File

@ -173,6 +173,28 @@ Direction:
- prefer `before_prompt_build` for prompt mutation work
- remove only after real usage drops and fixture coverage proves migration safety
### Compatibility signals
OpenClaw treats config validity and plugin migration state as separate axes:
- **config valid** — the config parses and referenced plugins can be resolved
- **compatibility advisory** — a plugin is still on a supported compatibility
path, such as `hook-only`
- **legacy warning** — a plugin still uses `before_agent_start`
- **hard error** — the config is invalid or plugin loading/validation fails
Current compatibility guidance:
- `hook-only` is advisory only. It remains a supported compatibility path for
existing plugins.
- `before_agent_start` is the only strong migration warning in the current
model.
- Neither state blocks an existing plugin by itself.
You can see these signals in `openclaw doctor`, `openclaw status`,
`openclaw status --all`, `openclaw plugins doctor`, and
`openclaw plugins inspect <id>`.
## Architecture
OpenClaw's plugin system has four layers: