docs: clarify reserved gateway method namespaces

This commit is contained in:
Peter Steinberger
2026-04-04 12:08:32 +01:00
parent 9b352ab5b0
commit 49bf527fd4
6 changed files with 30 additions and 0 deletions

View File

@@ -106,6 +106,11 @@ gateway starts listening.
the default behavior.
</Warning>
If your setup/full entry registers gateway RPC methods, keep them on a
plugin-specific prefix. Reserved core admin namespaces (`config.*`,
`exec.approvals.*`, `wizard.*`, `update.*`) stay core-owned and always resolve
to `operator.admin`.
## Plugin manifest
Every native plugin must ship an `openclaw.plugin.json` in the package root.
@@ -199,6 +204,9 @@ background services) during setup flows.
- Any HTTP routes required before gateway listen
- Any gateway methods needed during startup
Those startup gateway methods should still avoid reserved core admin
namespaces such as `config.*` or `update.*`.
**What `setupEntry` should NOT include:**
- CLI registrations