openclaw - 💡(How to fix) Fix Manifest-id mismatch warning fires for ~30+ built-in plugins on gateway start (xai, anthropic, brave, etc.) [2 pull requests]

Version: OpenClaw 2026.5.19 (commit a185ca2)

Summary

On gateway start, OpenClaw emits a plugin id mismatch warning for every built-in plugin whose entry hint (likely derived from the npm package or directory name) doesn't exactly match the id field in its openclaw.plugin.json manifest. This appears to be a naming-convention drift across the plugin catalog rather than a per-plugin bug. The plugins load and function normally — warnings are cosmetic — but the gateway logs ~30 of these lines per startup, which is operator log noise.

Example warning lines

From ~/.openclaw/logs/gateway.err.log, 2026-04-01T14:09:59:

Config warnings:
- plugins.entries.amazon-bedrock: plugin amazon-bedrock: plugin id mismatch (manifest uses "amazon-bedrock", entry hints "amazon-bedrock-provider")
- plugins.entries.anthropic: plugin anthropic: plugin id mismatch (manifest uses "anthropic", entry hints "anthropic-provider")
- plugins.entries.brave: plugin brave: plugin id mismatch (manifest uses "brave", entry hints "brave-plugin")
- plugins.entries.browser: plugin browser: plugin id mismatch (manifest uses "browser", entry hints "browser-plugin")
- plugins.entries.duckduckgo: plugin duckduckgo: plugin id mismatch (manifest uses "duckduckgo", entry hints "duckduckgo-plugin")
- plugins.entries.exa: plugin exa: plugin id mismatch (manifest uses "exa", entry hints "exa-plugin")
- plugins.entries.firecrawl: plugin firecrawl: plugin id mismatch (manifest uses "firecrawl", entry hints "firecrawl-plugin")
- plugins.entries.github-copilot: plugin github-copilot: plugin id mismatch (manifest uses "github-copilot", entry hints "github-copilot-provider")
- plugins.entries.google: plugin google: plugin id mismatch (manifest uses "google", entry hints "google-plugin")
- plugins.entries.xai: plugin xai: plugin id mismatch (manifest uses "xai", entry hints "xai-plugin")
... [~30 entries total]

Concrete xAI example

• Manifest: dist/extensions/xai/openclaw.plugin.json → "id": "xai"
• Package: dist/extensions/xai/package.json → "name": "@openclaw/xai-plugin"
• Entry hint inferred from the package name's basename → "xai-plugin" ≠ "xai"

Pattern

The convention appears to be:

• Manifest id: short, e.g. xai, anthropic, brave
• Package name: @openclaw/<id>-plugin or @openclaw/<id>-provider
• The entry-hint resolution presumably strips @openclaw/ and uses the rest as-is, producing the suffixed form

The warning fires because manifest-id and entry-hint don't string-match.

Suggested resolutions (pick whichever fits direction)

1. Update the manifest-id resolution to normalize-then-compare (strip -plugin / -provider suffixes before equality check).
2. Update manifest id to match package basename (xai-plugin, anthropic-provider, etc.) — wider change, touches id semantics across the catalog.
3. Downgrade this specific warning to debug level and only emit at startup when the operator opts into verbose plugin diagnostics.

Impact

None functional — all plugins load and run. Just operator log noise on gateway start.

Repro

1. Install [email protected] (or any recent version)
2. Start the gateway (openclaw gateway run)
3. Tail ~/.openclaw/logs/gateway.err.log and grep for plugin id mismatch