docs: clarify plugin gateway auto-restart

This commit is contained in:
Peter Steinberger
2026-05-16 17:11:44 +01:00
parent 777d289979
commit 15b0d43412
3 changed files with 24 additions and 15 deletions

View File

@@ -17,7 +17,7 @@ Most install workflows are:
1. find a package
2. install it from ClawHub, npm, git, or a local path
3. restart the Gateway that serves your channels
3. let the managed Gateway auto-restart, or restart it manually when unmanaged
4. verify the plugin's runtime registrations
## List and search plugins
@@ -82,7 +82,10 @@ target. For routine upgrades of tracked npm, ClawHub, or hook-pack installs, use
## Restart and inspect
After installing plugin code, restart the Gateway that serves your channels:
After installing, updating, or uninstalling plugin code, a running managed
Gateway with config reload enabled restarts automatically. If the Gateway is not
managed or reload is disabled, restart it yourself before checking live runtime
surfaces:
```bash
openclaw gateway restart
@@ -128,12 +131,12 @@ matching `@beta` releases. For the exact fallback and pinning rules, see
openclaw plugins uninstall <plugin-id> --dry-run
openclaw plugins uninstall <plugin-id>
openclaw plugins uninstall <plugin-id> --keep-files
openclaw gateway restart
```
Uninstall removes the plugin's config entry, persisted plugin index record,
allow/deny list entries, and linked load paths when applicable. Managed install
directories are removed unless you pass `--keep-files`.
directories are removed unless you pass `--keep-files`. A running managed
Gateway restarts automatically when the uninstall changes plugin source.
In Nix mode (`OPENCLAW_NIX_MODE=1`), plugin install, update, uninstall, enable,
and disable commands are disabled. Manage those choices in the Nix source for