← All fixes
OpenClaw· Agent errors

OpenClaw “conflicting plugin install metadata” (shared SQLite state) — how to fix

Left plugin install index in place because shared SQLite state has conflicting plugin install metadata for: …
Quick answer

This warning means an OpenClaw upgrade left the plugin registry half-migrated: the shared SQLite state and the plugin install index disagree about what's installed. It usually appears after a version upgrade (recent versions moved bundled providers into plugins) or an install that was interrupted, for example by a full disk. Running OpenClaw's doctor command and reinstalling the named plugin cleanly resolves it.

What causes it

How to fix it

  1. Run OpenClaw's doctor command — it detects and repairs inconsistent plugin state after upgrades.
  2. Reinstall the plugin named in the message so the install index and SQLite metadata are rewritten together.
  3. Check disk space first: a full disk during upgrade is a common trigger, and clearing space alone doesn't repair already-corrupted state.
  4. If it persists, back up your config, remove the conflicting plugin state, and let OpenClaw reinstall plugins from scratch.
Running an agent?

This is local agent state, not a model or provider problem — after cleanup, the same warning can reappear if auto-upgrade runs while a plugin install is in flight, so avoid upgrading mid-task.

FAQ

Is this error why my OpenClaw stopped responding?

It can contribute. A half-migrated plugin state makes failures look random — messages erroring, cron jobs not firing, API keys not being read. Repair the plugin state first, then re-test before blaming the model or provider.

Does clearing disk space fix it?

Not by itself. Low disk often triggers the corruption, but once plugin metadata conflicts, you need OpenClaw doctor or a clean reinstall of the named plugin — freeing space just prevents recurrence.

Related errors

OpenClaw “API rate limit reached” (429)OpenClaw · 429Why your AI agent keeps getting rate limited (and how to stop it)Any agent