Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
Every gateway restart shows two identical warnings about openclaw-weixin missing channelConfigs metadata, even when the plugin is disabled.
Steps to reproduce
- Install OpenClaw 2026.4.29
- Set plugins.entries.openclaw-weixin.enabled = false in openclaw.json
- Remove openclaw-weixin from plugins.allow in openclaw.json
- Run: openclaw gateway restart
- Observe startup output
Expected behavior
No warnings about openclaw-weixin should appear when the plugin is disabled and removed from plugins.allow.
If the warning is necessary, it should appear only once, not twice.
Actual behavior
Two identical warnings appear on every gateway restart regardless of plugin enabled state:
plugin openclaw-weixin: channel plugin manifest declares openclaw-weixin
without channelConfigs metadata; add openclaw.plugin.json#channelConfigs
so config schema and setup surfaces work before runtime loads
OpenClaw version
2026.4.29 (be8c246)
Operating system
macOS 26.3.1 (arm64)
Install method
npm global
Model
minimax/MiniMax-M2.7
Provider / routing chain
openclaw -> minimax/MiniMax-M2.7 (direct API, no gateway proxy)
Additional provider/model setup details
Using MiniMax-M2.7 via api.minimaxi.com with Anthropic-compatible endpoint.
openclaw-weixin plugin is disabled in plugins.entries and removed from plugins.allow.
Logs, screenshots, and evidence
Config warnings:
- plugins.entries.openclaw-weixin: plugin openclaw-weixin: channel plugin manifest declares openclaw-weixin without channelConfigs metadata; add openclaw.plugin.json#channelConfigs so config schema and setup surfaces work before runtime loads
- plugins.entries.openclaw-weixin: plugin openclaw-weixin: channel plugin manifest declares openclaw-weixin without channelConfigs metadata; add openclaw.plugin.json#channelConfigs so config schema and setup surfaces work before runtime loads
Impact and severity
Low severity - cosmetic issue only. The duplicate warnings appear on every gateway restart but do not affect functionality. The plugin is disabled and all features work normally. However, the noise makes it harder to spot real configuration issues in startup output.
Additional information
The warning persists even after:
- Setting plugins.entries.openclaw-weixin.enabled = false
- Removing openclaw-weixin from plugins.allow
- Removing openclaw-weixin from plugins.entries entirely
The warning appears to be triggered at config validation time before the plugin enabled state is checked, suggesting the channelConfigs metadata check runs unconditionally on all registered channel plugins.
Node: v24.15.0
Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
Every gateway restart shows two identical warnings about openclaw-weixin missing channelConfigs metadata, even when the plugin is disabled.
Steps to reproduce
Expected behavior
No warnings about openclaw-weixin should appear when the plugin is disabled and removed from plugins.allow.
If the warning is necessary, it should appear only once, not twice.
Actual behavior
Two identical warnings appear on every gateway restart regardless of plugin enabled state:
OpenClaw version
2026.4.29 (be8c246)
Operating system
macOS 26.3.1 (arm64)
Install method
npm global
Model
minimax/MiniMax-M2.7
Provider / routing chain
openclaw -> minimax/MiniMax-M2.7 (direct API, no gateway proxy)
Additional provider/model setup details
Using MiniMax-M2.7 via api.minimaxi.com with Anthropic-compatible endpoint.
openclaw-weixin plugin is disabled in plugins.entries and removed from plugins.allow.
Logs, screenshots, and evidence
Impact and severity
Low severity - cosmetic issue only. The duplicate warnings appear on every gateway restart but do not affect functionality. The plugin is disabled and all features work normally. However, the noise makes it harder to spot real configuration issues in startup output.
Additional information
The warning persists even after:
The warning appears to be triggered at config validation time before the plugin enabled state is checked, suggesting the channelConfigs metadata check runs unconditionally on all registered channel plugins.
Node: v24.15.0