Install Plugins Without Restarting the Gateway

v2026.9.5: you can install or reload supported plugins without bouncing the Gateway, from the Control UI or an authorized chat command. Existing permissions and consent carry over. Official manage-plugins docs are the command reference.

Docs: docs.openclaw.ai/plugins/manage-plugins. Control UI and Gateway RPCs apply plugin changes on the running process. CLI install/enable/disable/uninstall use the local running Gateway when it is up.

What still needs a restart

  • Rebuilt bundled plugin code. Explicit reload of a loaded bundled plugin can report restartRequired: true even if files look unchanged. Restart after you rebuild compiled output.
  • Enabling experimental native plugin UI (9.5 notes).
  • Offline installs: start the Gateway before you expect runtime surfaces.

Managed Codex conversations can stay alive when tools change; switching them stops the current turn and background terminals.

Operator commands

After a source or manifest edit, reload instead of reinstalling:

openclaw plugins inspect <plugin-id> --runtime --json
openclaw plugins reload <plugin-id>

If runtime application fails, the error distinguishes a rejected replacement from a change that published and then failed. An install can remain saved even when its runtime does not start. Fix the reported problem, then Reload in Lifecycle settings—or the CLI above. Repeating installation is unnecessary.

Default hybrid reload applies config saves under plugins.entries. to that plugin’s instance only. Unchanged plugins keep their instances. A plugin may declare a narrower policy that retains the instance or requires a restart.

Related