OpenClaw Plugin Not Loading

Separate package installation from effective activation. A package can exist on disk while being disabled, rejected by policy, incompatible, or unable to register its capability.

Inspect inventory and logs

openclaw plugins list
openclaw doctor
openclaw status --all
openclaw logs --follow

Confirm the exact package identity, source, version, enabled state, and capability name. Look for manifest, dependency, duplicate registration, compatibility, or configuration errors during Gateway startup.

Check policy and configuration

An explicit plugin allowlist can omit a newly installed plugin. A channel or browser root configuration may also be required to activate its bundled integration. Do not add a broad wildcard simply to make one plugin appear; add the verified identifier.

If the plugin registers a tool, its tool must also survive the effective tool profile. If it registers a channel or provider, verify that its required credentials and configuration exist.

Isolate the update

When failure began after an update, record both versions. Disable the plugin, verify Gateway health, then restore only the last known compatible version through the documented package path.

Expected result

• The plugin appears once with a known origin.
• Doctor reports no blocking manifest or dependency error.
• Gateway startup registers the expected capability.
• The capability is visible only where policy allows it.